[marknadal]

The "permanent web" has now just become "the most popular pinned web" like torrents did. :(

I really think we need to expand our use cases to included mutable and immutable content.

People simply are not going to switch to the dweb if they have to deal with this complexity.

I did a talk on this at the Internet Archive's Decentralized Web Summit a few months ago, and how we can fix this, alongside a bunch of others in the dWeb space like DAT, SSB, etc. ( https://www.decentralizedweb.net/videos/talk-better-algorith...).

[diggan]

> The "permanent web" has now just become "the most popular pinned web" like torrents did. :(

That'd be great! Torrents are great for keeping content alive, and if it's not alive (not having any seeds), you can find someone who had the content before to just start their client, add the content again and all the content is still referred the same way. I remember a while back on HN, the oldest torrent was discussed but unfortunately it didn't have any seeds. The original author of the content saw this, and started it's node, allowing people to download it again, without having to pass around new links/IDs. I think it was a Matrix remake called "The Fanimatrix", but I can't find the comment anymore. Torrents are great for making sure content is available for a long time, something the current web suck at.

Imagine the same with websites. Rather than Yahoo deciding for the world that Geocities shouldn't be online anymore, people can decide to help out to host it, and no links would change. That's a future I can get behind! Would make it super easy to recover websites, compared to our current ways (hoping that Internet Archive have previously archived the website)

> I really think we need to expand our use cases to included mutable and immutable content.

> People simply are not going to switch to the dweb if they have to deal with this complexity.

Agree with both points! And I think I specifically have told you this before as well here on HN, IPFS does support dynamic content out-of-the-box with pubsub and raw streams to other peers. However, the basic building blocks IPFS provides, aren't really meant to replace the currently easy experience of web development.

For a better developer experience, there are libraries wrapping IPFS. Examples include https://github.com/ipfs-shipyard/peer-star-app/blob/master/d... and https://github.com/orbitdb/orbit-db/, both very easy to use.

Disclaimer: I work for Protocol Labs on IPFS and related projects

[buboard]

if anything, torrents / ipfs lend themselves naturally to the way human culture was always disemminated: if something is popular and lasting, it was passed on for generations, some trivial stuff that literally nobody cares about was naturally lost. Since we can't expect the huge amounts of data created every day to be archived forever, this is a very natural way to keep only the most interesting parts.