Q.U.I.N.N. on Nostr: it got hyped for the nft craze and people set up businesses where you paid people to ...

it got hyped for the nft craze and people set up businesses where you paid people to keep your nfts hosted. i'm not aware if they are still around because i didn't use them. anna's archive and dhall used ipfs as a backing store and both dropped it for questionable reasons.

anna's went to russian file lockers where you pay money for privileged access so its questionable how much that choice was legitimate vs rent seeking.

dhall argued about it for a while because it provided decentralization from github; then went back to github as a CDN because of "performance issues" (large directories aren't optimized well.)

i think Blurry Moon (npub1hjv…drdr) used it and didn't like the daemons. though there were pinset orchestrator progs. it did get used to distribute 2077 leaks and such.

ipfs is sort of a walking corpse at the moment. it works, but its obviously less optimal than what "just use cloudflare bro" can ever provide, and the one major consumer pushing it (NFTs) was killed. brave tinkered with supporting it and i think since killed that too.

there's some forks and rewrite attempts aimed at fiddling with the directory problem. i know they added support for buzhashes and such, so you can actually do contentful chunking of websites and feed fragments of files you have that are unchanged with a different version of the site.

ultimately it needed a UX where a browser could report it supported ipfs, or a server broadcast that it did, and the browser would offer a little thumbtack button to pin some site. i think i have a draft x-accept-cdn: ipfs / x-accept-ipfs on my website. but getting browsers to do anything is impossible without a corporate spire forcing their hand, so.