@jeekajoo shaarlinks 30/05/2015
https://github.com/cjb/GitTorrent/blob/master/README.md

Quand on utilise la commande git avec 'toto://' comme protocole, ça appele 'git-remote-toto'. Pour ces 3 cas, ça va donc taper sur git-remote-gittorrent:
"""
   gittorrent://some.git.hosting.site/somerepo -- we connect over git:// to find out what the latest commit is, then perform the download using that commit's sha1. This is kind of like a CDN for a git server; the actual download of objects happens via peers, but the lookup of which objects to downloads happens in the normal Git way.

   gittorrent://<hex sha1>/reponame -- the sha1 corresponds to a gittorrent user's "mutable key" (hash of their public key) on our DHT -- we look up the key, receive JSON describing the user's repositories, and then perform the download using that commit's sha1. This doesn't use any resources outside of GitTorrent's network.

   gittorrent://<username> -- the username is converted into a mutable key sha1 as above. The mapping from usernames to happens on Bitcoin's blockchain in OP_RETURN transaction.
"""
(Permalink)