Yes, IPFS addresses some of the use-cases of HTTP while solving other problems where HTTP falls short. It isn't a complete drop-in replacement, but does set up a foundation for an internet that will last longer and (at some point) perform better across varying network conditions.
> but I think this is (vaguely) analogous to building
> a website based on IP addresses and port numbers, not URIs.
IPNS is a naming solution designed to address this:
It's not super fast right now, but there's some work happening now to make it much faster.
ENS, the Ethereum name system, is also an emerging way of doing this.
> basically be this URI resolution map
IPLD is a data model that works with IPFS to address the use-case you're describing, where you have a permanent reference to a mutable set of data: https://ipld.io/
All right so there is already work ongoing to solve these problems, and that work is built on top of IPFS instead of extending the base protocol, and the author who just insisted using plain IPFS was thus suffering from expected difficulties as IPFS really isn't the direct answer to that particular usecase.
> but I think this is (vaguely) analogous to building > a website based on IP addresses and port numbers, not URIs.
IPNS is a naming solution designed to address this:
https://docs.ipfs.io/guides/concepts/ipns/
It's not super fast right now, but there's some work happening now to make it much faster.
ENS, the Ethereum name system, is also an emerging way of doing this.
> basically be this URI resolution map
IPLD is a data model that works with IPFS to address the use-case you're describing, where you have a permanent reference to a mutable set of data: https://ipld.io/