[bArray]

> As for RSS, well, as HN custom insists, I am also

> commenting to plug my own fraidyc.at. See, you knew it was

> here.

This is quite a nice implementation and the back story is cool.

I have also been thinking about this for some time, but what I want to achieve is decentralized RSS feeds. Servers go down over time, are blocked or suffer some other issue. I want to be able to help keep alive the content I consume, possibly without the need for centralization.

Ideally the aim would be to maintain backwards compatibility and be as decentralized as possible, but I'm still yet to solve this problem without resulting to just using torrents.

[MayeulC]

Have a look at the beaker browser suggested in the parent post. It uses the hypercore protocol (new name for the dat protocol), which allows one to build collections of data, update them, and have them mirrored over a DHT, kind of like IPFS does. You can choose to contribute to mirroring some content you like, if you want to :)

Of course, ideally, the websites themselves would publish articles on the hypercore network, and be the source of trust here, but I don't see why you couldn't do it from RSS feeds.

I am not sure whether the data is content-addressed on hypercore? If so, multiple people could archive the same content to make sure it is identical, and still enjoy the benefits of distributed hosting :)

More about hyperdrive/hypercore: https://news.ycombinator.com/item?id=23180572