Lmst

@akatsukilevi @kat Personally, I've heard once of #GitTorrent before but like #BitMessage found it to be clunky, slow and ugly af.

#Blockchains - espechally #Bitcoin - are not efficient at handling many small transactions as is commonplace in #Git, and for #Authentification, #PGP and #SSH do work way better...

OFC someone could rework that to use #Solana or other stuff but I don't like #Shitcoins and the only #Cryptocurrency that I can take serious is #Monero which is designed to not allow tracking users and transactions!

Seems like #GitTorrent was abandoned a few years ago, or at least the GH repo was. Maybe the work got merged into or superseded by #Git-SSB?

@sir #GitTorrent is one attempt to solve the decentralized GH problem, your #sr.ht is another, #GitPub is another, #Git-SSB is another (https://github.com/noffle/git-ssb-intro). Each one tries using a different standardized of protocols (#BitTorrent, email, #ActivityPub, #SSB). Ideally it would be possible to bridge them all, so users and projects could hosted anywhere, and users could contribute anywhere

@kmicu yeah, we need this dearly. There was #GitTorrent, not sure if still supported. Also, #gx is interesting: https://github.com/whyrusleeping/gx

What I dislike about #gitlab, #gitea, #gogs and other similar projects is that any user who wants to contribute to one of your repos must create an account in your instance. So, you are forced to run a public instance. It's unpleasant business to run large public instances. It becomes a single point of failure. And, benefits of decentralization are diminished or lost.

We need something P2P or federated for hosting git. Some approaches I've heard of are #gittorrent, git over #ipfs, #bugseverywhere and #ditz. However, many of these projects are inactive and don't seem to be maintained. :-(

#GitTorrent

Client Info