IPFS problems: Too much immutability

Content-addressing is unusable with an index or database that describes each piece of content. Since IPFS is fully content-addressable, nothing can be done with it unless you have a non-IPFS index or database, or an internal protocol for dynamic and updateable links.

The IPFS naddr1qvzqqqr4gupzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqyghwumn8ghj7enfv96x5ctx9e3k7mgqpp3xgep3vd3nyvc0phjk9 made then go with the with the second option, which proved to be naddr1qvzqqqr4gupzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqyghwumn8ghj7enfv96x5ctx9e3k7mgqpqmxye3ex5mnjcgkv23dr. They even incentivized the creation of a database powered by IPFS, which couldn't be more misguided.