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: https://codeberg.org/Safeguarding/-/projects/19508

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."

#bittorrent #sciop

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 people 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.

Sciop is as easy to run as a bittorrent client. The idea will be to have it serve as a companion to a client, where we are going to implement a minor mutation of the FEP for mobile identity so you can mirror an identity from your personal client companion to any other instance that chooses to mirror yours. So this isn't like "come help our website" this is "get the fun parts of this website ready for when it's time to talk to other websites"

#sciop