4 ms·
Their torrents suck and IME don’t update to changes in the archive.
by tourmalinetaco 2y ago
Their torrents suck and IME don’t update to changes in the archive.
- vundercind 2y agoThis is accurate, their torrent-generating system is basically broken to the point of being useless.
- addandsubtract 2y agoAren't torrents terrible at handling updates in general? If you want to make a change to the data, or even just add our remove data, you have to create a new torrent and somehow get people to update their torrent and data as well.
- blurbleblurble 2y agoThere's a mutable torrent extension (BEP-46) but unfortunately I don't think it's widely supported. I think IPFS/IPNS is the more likely direction.
- tourmalinetaco 2y agoWhich IA has moved into and hasn’t found much luck in, unfortunately.
- jpk 2y agoHow come?
- rbanffy 2y agoTorrents are immutable in principle, which is good for preserving things. A new version of a set of files should be a new torrent.
- zelphirkalt 2y agoHow would preservationists go about automatically updating the torrent and data they seed? Or would they need to manually regularly check, if they are still seeding the up-to-date content?
- diggan 2y ago> Torrents are immutable in principle In practice, that's mostly how they're being used. But the protocol does support mutation. The BEP describing the behavior even has archive.org as an example... > The intention is to allow publishers to serve content that might change over time in a more decentralized fashion. Consumers interested in the publisher's content only need to know their public key + optional salt. For instance, entities like Archive.org could publish their database dumps, and benefit from not having to maintain a central HTTP feed server to notify consumers about updates. http://www.bittorrent.org/beps/bep_0046.html http://www.bittorrent.org/beps/bep_0046.html
- account42 2y agoSpecs are nice but does any client actually implement this?