In the future, one of the things we should plan for is that bittorrent makes civilian participation in and contribution to emergency backup efforts a lot easier than any other technology layer we have to hand.
A question: What is a good approach to "torrent-style distribution supporting incremental change"?
In my ill-informed mind this looks something like rss where your subscription is an initial seed, followed by subsequent torrents each of which has an incremental set of diffs/overlays, so you can update torrents without throwing away existing work or contributions.
Does something shaped like that exist already?
Edit: Rsync, I know, but rsync isn't "set-and-forget" the same way.
@mhoye BitTorrent itself support it: https://www.bittorrent.org/beps/bep_0046.html
Also, that was the main intent design of IPFS. See https://docs.ipfs.tech/concepts/ipns/
https://hypercore-protocol.org/ might be a solution.
@lutindiscret Yeah IMO the Pear/Holepunch ecosystem is much better equipped for this. One can pull changes from a Hyperdrive in near realtime with authenticity built into the publisher and automatic spread accross the network. Making a client for it is pretty easy. Also a p2p web app from within @agregore could save on the hassle of making it cross platform and auto updateable.
