That’s what Brave does built in, and other browsers with the ipfs companion extension
When you hit a ipfs URL it’s resolving it either through a gateway or through your own node
We'd really need some support from Firefox/Chrome/Safari trio to really start adoption. Most likely Firefox, then (albeit unlikely) Chrome and Safari.
Brave's adoption is just too low, even though I (and probably a significant people here ar HN) personally think it's doing the best.
Most global browser share numbers I could find bundled Brave into the "Other" category - this was the only one I found that broke it out separately: https://kinsta.com/browser-market-share/
- Brave at 54M MAU: https://basicattentiontoken.org/growth/
Out of my hands but getting more browsers than Brave to add support seems like the next place to start pushing IMO.
Brave browser has ipfs support built in and I think there are plugins for chrome and firefox without the code localy to do p2p properly it doesn't really make much sense faking it with WebRTC when the end result is the same as using a gateway directly.
It can even "polyfill" any IPFS paths automatically (which should just be simply as replacing any ipfs:// URIs with ipfs.io gateway paths).
For anyone trying to host pinned files behind a NAT/CGNAT would it be possible to hole punch to serve paths directly? If possible everything can me set up to work just out of the box with minimal/no setup in browser which should be the aim.
In other words, we need something of an IPFS version of what MetaMask/ethers.js did to Ethereum based blockchains.