[jeroenhd]

The ideas behind IPFS definitely seem to reflect the unchangeable URL intentions of this article. However, IPFS is also more limited, as edits and updates require special handling and interactivity is simply not possible.

Furthermore, IPFS is too slow to be usable in practice. I'd love it to become a serious alternative to the web in terms of documents and blog posts, but the amount of timeouts and 30+ second loading times you need to tolerate to get any IPFS page to load makes it very difficult to tolerate.

At least with the NFT scams IPFS found a real-life purpose, something I hadn't expected to see. That's dying down now, I think, so who knows how long the most active pin servers will stick around.

[fabrice_d]

IPFS would still be a good candidate for media attachments in Mastodon, potentially saving quite a bit of resources in bandwidth and storage.

The performance of ipfs gateways has improved a lot lately, so even without a native ipfs:// protocol handler that could work nicely in clients.

[rakoo]

Bittorrent has been there for decades and can solve the issue ofedia attachments way more easily than ipfs

[fabrice_d]

Are there gateways to access bittorrent resources from https:// ?

[rakoo]

There are multiple libraries and software giving you a gateway, but there's no public gateway. It would fall into problematic use in less than an hour because of the insanity that IP is, and it would completely contradict the whole idea of being decentralized

[dmitriid]

If no one is paying, content on IPFS will disappear, and very soon.