Git really should be married with bittorrent for large files. At the moment it’s GFS which requires large central storage, which doesn’t really fit with git. Should be maglinks.
Or IPFS. The issue in this context is that bittorrent would treat each version as a unique collection of files and you can’t combine seeding of redundant files. IPFS has much better means to handle updates.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
The fediverse can’t reach source forges fast enough…
Git really should be married with bittorrent for large files. At the moment it’s GFS which requires large central storage, which doesn’t really fit with git. Should be maglinks.
Or IPFS. The issue in this context is that bittorrent would treat each version as a unique collection of files and you can’t combine seeding of redundant files. IPFS has much better means to handle updates.
Git LFS exists, not sure how it works technically, but it’s what the AI people use for AI model VCS.
So does using maglinks, it exists in git-annex. It’s just the torrent client is super crap. Great idea, poorly implemented.