3 ms·
The problem I see with the torrent approach being that you need to reach a consensus eventually, right? If I push a commit on the main branch, share that state,
by palata 3y ago
The problem I see with the torrent approach being that you need to reach a consensus eventually, right? If I push a commit on the main branch, share that state, and you do the same with a different commit, then we have a conflict that we need to solve...
- hackernudes 3y agoThere would have to be a canonical source of truth (with private key). Then one could be reasonably sure an update is blessed by the owner. Makes me think of nostr + git + torrent/ipfs.
- palata 3y agoOh right. Not everyone modifies the torrent, then, just the maintainer. So as a user I get the magnet link, download (clone) the repo over torrent, then I can send a patch to the maintainer over email, discuss it there (maybe on a mailing list), and when the maintainer merges it, they can update the torrent and propagate the new state of the history. Is that about right? It actually sounds cool :-). I guess the next issue I see is that torrents are not mutable (I think there are some specs maybe, but it's not common/implemented? Not sure).