I have always wondered about IPFS and its relationship with DNS.

What's stopping authoritarian entity from poisoning/redirecting ipfs.io to static page?

Nothing, but that would hopefully primarily encourage people to set up IPFS clients themselves instead of relying on the public bridge.

(Which is IMHO one of the weaknesses of IPFS, that they haven't made that more prominent/easier, through browser plugins or a dedicated IPFS-browser. Compare to e.g. the publicity boost Dat got from Beaker Browser)

This is a very nice Chrome extension:

https://chrome.google.com/webstore/detail/ipfs-station/kckhg...

It'll redirect all IPFS URLs to your local daemon.

Ohh, interesting, that seems to have most of the things I was looking for. Not sure why I missed it when I went looking for one recently. Thanks!

No problem, I had missed it too but someone here pointed me to it. I wish we had one for Firefox as well!

What stops that one from running in Firefox? I haven't dug into its code, but nothing in its description or screenshots looks like the FF web extension implementation shouldn't support it. I mean, it's just a little chrome, a content script doing link rewrites, and an occasional HTTP request to fetch status info, yeah?

Nothing stops it, I guess it's just that nobody has bothered to make one yet. It's works exactly as you describe, though, pretty simple.

https://www.ghacks.net/2016/05/23/install-google-chrome-exte... might be worth a look. Haven't tried it, but the claim is that it mechanically transforms Chrome extension metadata and containers into Firefox's formats, and supports automatic signing via AMO for permanent installation. Assuming that, the rest should Just Work modulo possibly still incomplete WebEx API support in Firefox. If you try it, I wouldn't mind hearing how you get on.

Holy hell, it just worked! That's amazing, thank you for that. I bet it helps that the extension is just redirecting and collecting stats, but everything seems to work fine!

That's great to hear! Most welcome, and glad to know there's a plausible option - with the rapid deprecation of the old API, this might save a lot of time. (I can't rely on replacing all my old extensions with shell oneliners, after all...)

Nothing, but what does it matter? There are loads of public gateways. I run one at https://www.eternum.io. Also, running your own node is trivial.

It's pretty trivial to run an IPFS gateway as a Tor hidden service. Also IPFS branches into Tor OnionCat's IPv6 /64. And nodes that link resources between clearnet and OnionCat /64. Or any other overlay network.