if anyone is bored or wants to contribute to gray archive tech, i've done all the hard parts around this, but here is a set of things you could do to make "practical repack mutability for torrents" happen: codeberg.org/Safeguarding/-/pr

so we have an indexer and a cli tool that can interact with clients. if we added one link table that allowed people to declare relationships between torrents - like e.g. if one replaces another, or is an updated version of, successor to, and so on, then one could plug in the pieces so the cli periodically checks for updated versions of torrents and swaps them out in the local client.

this could be your name in the credits: "what if bittorrent trackers weren't just static repositories of torrent files and generic peer connection machines but could facilitate socio-technological resolutions to basic problems in the protocol."

yes, DHT-flavor mutable torrents exist, but i have never ever seen them used in practice in a publicly accessible way. this is something where we are building towards recognizable peers being able to update, remix, replace, etc. a given dataset... first just by handling self-repacks, but then the goal will be to just model the graph of relationships between things.

0

If you have a fediverse account, you can quote this note from your own instance. Search https://neuromatch.social/users/jonny/statuses/114748961959694498 on your instance and quote it. (Note that quoting is not supported in Mastodon.)