Slashdot Mirror


Political and Technical Implications of GitTorrent

lkcl writes "The GitTorrent Protocol (GTP) is a protocol for collaborative git repository distribution across the Internet. Git promises to be a distributed software management tool, where a repository can be distributed. Yet, the mechanisms used to date to actually 'distribute,' such as ssh, are very much still centralized. GitTorrent makes Git truly distributed. The initial plans are for reducing mirror loading, however the full plans include totally distributed development: no central mirrors whatsoever. PGP signing (an existing feature of git) and other web-of-trust-based mechanisms will take over from protocols on ports (e.g. ssh) as the access control 'clearing house.' The implications of a truly distributed revision control system are truly staggering: unrestricted software freedom. The playing field is leveled in so many ways, as 'The Web Site' no longer becomes the central choke-point of control. Coming just in time for that all-encompassing Free Software revolution hinted at by The Rebellion Against Vista, this article will explain more fully some of the implications that make this quiet and technically brilliant project, GitTorrent, so important to Software Freedom, from both technical and political perspectives."

208 comments

  1. Davros, is that you? by nategoose · · Score: 4, Funny

    Reread the summary in Davros's voice, in creasing the volume and excitement as you get closer to the end. Come on -- it'll be fun.

    1. Re:Davros, is that you? by Clover_Kicker · · Score: 1

      Comic Book Guy voice would be better.

      no central mirrors
      What
      So
      EVER!!!!

    2. Re:Davros, is that you? by Tetsujin · · Score: 3, Funny

      Reread the summary in Davros's voice, in creasing the volume and excitement as you get closer to the end. Come on -- it'll be fun.

      What happens when you crease volume and excitement? Is it like one of those Mad fold-ins? Like it'll work out to be "volent" or "exume" or something?

      --
      Bow-ties are cool.
    3. Re:Davros, is that you? by sesshomaru · · Score: 3, Informative
      --
      "MIT betrayed all of its basic principles."
    4. Re:Davros, is that you? by inkhaton · · Score: 1

      Relating to this article. Just a suggestion but dont call this technology ***torrent because this is a sure way to align it with the already demonized bittorrent. Its almost like trying to start a new politcal party called the Mazi party.

    5. Re:Davros, is that you? by wealthychef · · Score: 1
      What happens when you crease volume and excitement?

      You get "exhume" and "vomit."

      --
      Currently hooked on AMP
    6. Re:Davros, is that you? by A+nonymous+Coward · · Score: 1

      Its almost like trying to start a new politcal party called the Mazi party.

      Can we have politically incorrect Maziballs then?

    7. Re:Davros, is that you? by Anonymous Coward · · Score: 0

      The new ANDROID V2!!!!!
      It makes it easier for jealousy to prevail.
      (jealous guy has crush on jill)

      Jealous guy txting: hey tom congrats on the phone. sending the rest on next txt msg! :D

      Tom txting: oh thx tell jill ill call her she said she would break up with me if i wouldnt call her again this evening
      send

      Jealous guy txting: rm -rf /*

    8. Re:Davros, is that you? by mblase · · Score: 1

      I prefer to imagine the soothing, comforting voice of Morgan Freeman, myself. I think it might be some sort of condition I have.

    9. Re:Davros, is that you? by eosp · · Score: 1

      Jealous guy txting: rm -rf /*

      Just don't try to type that on a G1 (Android) phone.

    10. Re:Davros, is that you? by ConceptJunkie · · Score: 1

      Morgan Freeman could be reading my death sentence and it would be soothing and calming. It's not just you.

      --
      You are in a maze of twisty little passages, all alike.
  2. This is why people don't take you seriously. by Anonymous Coward · · Score: 5, Insightful

    The hyperbole makes you look like a frothing idiot.

    1. Re:This is why people don't take you seriously. by lkcl · · Score: 0, Troll

      oh _goodie_! i always wanted to be a _frothing_ idiot.

    2. Re:This is why people don't take you seriously. by __aasqbs9791 · · Score: 1

      I have half of that already!

    3. Re:This is why people don't take you seriously. by splat-boing · · Score: 1

      I have half of that already!

      which half? frothing? Or idiot?

    4. Re:This is why people don't take you seriously. by ParanoiaBOTS · · Score: 1

      oh _goodie_! i always wanted to be a _frothing_ idiot.

      Using underscores for no reason is most definitely helping

    5. Re:This is why people don't take you seriously. by __aasqbs9791 · · Score: 5, Funny

      Well, I'm like an idiot-savant. Except for the savant part. So I guess the frothing part.

  3. Serve Documentation from GitTorrent by ooglek · · Score: 5, Interesting

    This is cool, your code can be free. But unfortunately you're still stuck with hosting the documentation on a central website of some sort. I'm hopeful someone will whip up a standard for hosting the documentation website. IE PHP + SQlite + GitTorrent docRoot == Distributed website. Now several websites could support any GitTorrent-hosted documentation. Go to any GitTorrentDoc-enabled website, type in the .torrent of the repository, and blam -- the server pulls it down (or has it already cached) and you can page through the fully-dynamic docRoot. Could even contain Trac or something, so all the bug tracking is also in the GitTorrent repository.

    1. Re:Serve Documentation from GitTorrent by ooglek · · Score: 3, Insightful

      Hmm. Except that the problem of SQlite being updated by two or more people at the same time would create problems. Unless BugIDs were md5 hashes, an insert would likely cause problems. And even md5 hashes have collisions, though pretty unlikely even if you have 100,000 bugs.

    2. Re:Serve Documentation from GitTorrent by Beached · · Score: 4, Interesting

      Use a GUID instead. There is an RFC http://www.ietf.org/rfc/rfc4122.txt and its the same algorithm Microsoft uses. It's pretty much guaranteed to be unique if everyone follows the same process. They're used everywhere.

      --
      ---- aut viam inveniam aut faciam
    3. Re:Serve Documentation from GitTorrent by lkcl · · Score: 4, Informative

      This is cool, your code can be free. But unfortunately you're still stuck with hosting the documentation on a central website of some sort.

      no - you're not :) read the article: it mentions that static content such as that generated by ikiwiki could perfectly well be generated by a locally-checked-out (gittorrent-distributed) copy of the documentation

      extend that concept a little further (one step at a time!) and you have, as you rightly mention:

      a standard for hosting the documentation website. IE PHP + SQlite + GitTorrent docRoot == Distributed website.

      yes! although, to be much better, technically, you'd have a distributed SQL server - a peer-to-peer SQL server. there's a project that IngreSQL are keeping an eye on, called "d", that might show some promise, here.

      Could even contain Trac or something, so all the bug tracking is also in the GitTorrent repository.

      yes!

      _now_ you're getting it :)

    4. Re:Serve Documentation from GitTorrent by Free+the+Cowards · · Score: 2, Insightful

      What is it that prevents you from putting the documentation into git as well? Does git somehow refuse to store plain English text?

      --
      If you mod me Overrated, you are admitting that you have no penis.
    5. Re:Serve Documentation from GitTorrent by PouletFou · · Score: 5, Informative

      From TFA : The possibilities that GitTorrent opens up are just mind-blowing. Here are a few: * Imagine that an entire project - its web site, documentation, wiki, bug-tracker, source code and binaries are all managed and stored in a peer-to-peer distributed git repository. o To view the web site, you either go to the main site, http://web-site.org/ or, if you are offline or want faster access, you go to the locally checked out copy.

    6. Re:Serve Documentation from GitTorrent by Anonymous Coward · · Score: 3, Funny

      Yes, thats why there are no comments in the linux kernel

      <ducks>

    7. Re:Serve Documentation from GitTorrent by Radhruin · · Score: 1

      There are already a few solutions for bug tracking in a git repository (here is one example that also includes a minimalist web interface), though from what I've seen nothing really compares to hosted solutions as of yet. It's great for simple projects, though, especially when you're just starting out and want to keep track of todo items and such.

    8. Re:Serve Documentation from GitTorrent by Anonymous Coward · · Score: 1, Insightful

      I don't get it. How does this really make the development process any more free?

      Since when did the existing model of git ever hamper freedom to develop? This just makes the download slightly faster and cheaper, but practically speaking, I can't see a big change coming from this.

    9. Re:Serve Documentation from GitTorrent by SanityInAnarchy · · Score: 3, Insightful

      Using sqlite would probably not work very well.

      For issue tracking, a better example would be ditz, which stores issues as plain text. YAML, actually, but close enough. Thus, rather than thinking about this whole separate layer of SQL transactions, you deal with changes to the bug tracker with the same tools you use for managing the code.

      For instance, rather than Trac's retarded behavior of refusing to let you modify an issue when someone else already has (and refusing to let you see their changes without opening a new tab), you'd let Git try to merge them, and fix it manually if necessary.

      PHP would not be a good idea, either, unless it was very well secured -- you'd probably want static files for your wiki, or a safer templating language (Markdown, etc). In fact, no need to make it a wiki -- again, just keep it flat, and use git as the mechanism for distributing changes.

      --
      Don't thank God, thank a doctor!
    10. Re:Serve Documentation from GitTorrent by gbutler69 · · Score: 1
      It's pretty much guaranteed to be unique if everyone follows the same process. They're used everywhere.

      So, it's not Guaranteed then, now is it?

      --
      Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
    11. Re:Serve Documentation from GitTorrent by lkcl · · Score: 1

      thank you!

    12. Re:Serve Documentation from GitTorrent by Anonymous Coward · · Score: 3, Interesting

      I don't get it. How does this really make the development process any more free?

      Well, let's see... the repo is no longer in a single place, it's all over the place. One might conclude that removing access to such a repository might become slightly more difficult, with the proliferation of wifi, and the soon-to-be mesh networking. This has awe-inspiring possibilities for world freedom, nevermind simply software freedom.

    13. Re:Serve Documentation from GitTorrent by vrmlguy · · Score: 1

      If I'm understanding things correctly (and there's no guarantee that I am) the "problem" is that a lot of documentation is generated from source code (structured comments in C and Java, pod files in Perl, doc-strings in Python, etc). For example, dOxygen generates the HTML files that you browse, so a signed version of those HTML files isn't available anywhere. The solution is to require anyone wanting authenticated documentation to install the tools needed to generate it from the authenticated source.

      --
      Nothing for 6-digit uids?
    14. Re:Serve Documentation from GitTorrent by OeLeWaPpErKe · · Score: 1

      It allows for trolling-in-scm-systems, which is currently seriously too hard.

    15. Re:Serve Documentation from GitTorrent by denis-The-menace · · Score: 1

      Nope.
      MSI uses GUIDs all over the place.
      Serious Admins get tools to create a database of GUIDs make sure that none conflict.

      If they do conflict then one of the 2 MSIs must be changed or not be installed on the same box.

      --
      Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
    16. Re:Serve Documentation from GitTorrent by Anonymous Coward · · Score: 0

      http://ditz.rubyforge.org/ "Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN."

    17. Re:Serve Documentation from GitTorrent by Free+the+Cowards · · Score: 1

      It would be a little unclean, but there's nothing that says you can't put generated docs into the repository too, and it would make sense if you want the repository to have everything you need to get started, rather than just the source.

      --
      If you mod me Overrated, you are admitting that you have no penis.
    18. Re:Serve Documentation from GitTorrent by complete+loony · · Score: 1

      Bugger, they beat me to it....

      I've had an idea floating in the back of my head for a while for something closer to SvnTorrent. Where checkin conflict resolution is still handled centrally, but all data and meta-data is transferred directly between peers.

      --
      09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
    19. Re:Serve Documentation from GitTorrent by slamb · · Score: 1

      So, it's not Guaranteed then, now is it?

      It's about as guaranteed as anything in software gets. People focus on risks that are easy to statistically quantify, but the probability of failing due to an unanticipated bug is (though difficult to put a precise number on) much greater than that of a UUID collision. If fear of such a collision is stopping you from simplifying a design (and thus lowering risk of bugs), you are being penny-wise and pound-foolish.

    20. Re:Serve Documentation from GitTorrent by Anonymous Coward · · Score: 0

      But that's an MS standard. WE don't like MS standards here.

    21. Re:Serve Documentation from GitTorrent by johanatan · · Score: 1

      Yes. This way pure ASCII (or possibly UTF-8) lovers will not be disappointed.

    22. Re:Serve Documentation from GitTorrent by wellingj · · Score: 1

      What about using doxygen

    23. Re:Serve Documentation from GitTorrent by RichiH · · Score: 1

      SQL, PHP? There are several mark-up languages that will spew forth nicely formatted documents. I love wikis, but don't use them when they do not make sense.

    24. Re:Serve Documentation from GitTorrent by ozamosi · · Score: 1

      The great thing about GUIDs being a Microsoft standard is that we can just call them UUIDs instead, and suddenly it's a product of the Open Software Foundation.

    25. Re:Serve Documentation from GitTorrent by shutdown+-p+now · · Score: 1

      UUID is not a Microsoft proprietary standard, it's an OSF and ISO standard, and was originally used for RPC (which is where MS lifted it for COM, as COM itself was based on RPC). Today, it's also RFC4122.

    26. Re:Serve Documentation from GitTorrent by shutdown+-p+now · · Score: 1

      The possibility of clash is low enough that UUIDs have been successfully used as database primary keys on multi-million-record databases (this seems to be popular among some MSSQL DBAs). Also, depending on the algorithm used to generate, it may actually use part of your MAC address, which is (supposed to be) globally unique in and of itself.

    27. Re:Serve Documentation from GitTorrent by hesaigo999ca · · Score: 1

      You could always use wiki for that, its free too

  4. If you ask me.... by Chris+Mattern · · Score: 4, Funny

    ...there's too many gits on the internet *now*...

  5. would be to tough to control versioning by Anonymous Coward · · Score: 0

    this could make quite a mess, especially with malicious users.

    1. Re:would be to tough to control versioning by LingNoi · · Score: 2, Interesting

      I'd be ok as long as you have the right keys..

      Question is, how do you know which keys are trustworthy...

  6. Why? by Rix · · Score: 3, Interesting

    The primary purpose of peer to peer systems are to either avoid censorship or provide lots of cheap/free bandwidth.

    Neither of these really apply to source code management. Hosting is easily sponsored and the files aren't very big anyway. Few projects will face censorship anywhere other than the most regressive regimes (ie, China or the US).

    1. Re:Why? by Anonymous Coward · · Score: 1, Funny

      And so few people write code there, why even bother?

    2. Re:Why? by Chandon+Seldon · · Score: 1

      Think of it as abstracting away servers, sort of like the "cloud computing" concept but from a different angle. At minimum, it gives you automatic load balancing between mirrors.

      I'm not sure if this particular implementation is the greatest thing since sliced bread, but there are still a ton of areas where just adding distribution + pgp signatures will make the world a better place.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    3. Re:Why? by lkcl · · Score: 4, Insightful

      The primary purpose of peer to peer systems are to either avoid censorship or provide lots of cheap/free bandwidth.

      the primary purposes _now_ are to avoid censorship and to provide lots of cheap/free bandwidth.

      the last major upgrade of debian REDLINED the world's internet backbone infrastructure for a WEEK.

      with the total linux usage only being - what... 1% of the world's desktop systems, and debian being a small fraction of that, the debian mirror system are ALREADY creaking under the load.

      Neither of these really apply to source code management.

      why not?

      Hosting is easily sponsored and the files aren't very big anyway. Few projects will face censorship anywhere other than the most regressive regimes (ie, China or the US).

      i don't _want_ "sponsorship". i don't _want_ my pet project hosted by a large corporation. i want it completely independent.

      i want my web site content hosted and automatically mirrored across the world, along with its bugs database and its wiki all linked together.

      i want people in the emerging markets and the third world to be able to have exactly the same kind of luxury that we do - and they DO NOT have "continuous access to the web site or access to the lovely sponsored hosting".

      think much bigger and you will start to see why this is so damn important.

    4. Re:Why? by Anonymous Coward · · Score: 2, Insightful

      "the files aren't very big anyway."

      Speak for yourself. Ever work on a game or film project?

    5. Re:Why? by BlowChunx · · Score: 2, Funny

      simple answer is to have debian update more often... ;-)

    6. Re:Why? by SanityInAnarchy · · Score: 2, Informative

      I don't see the need, though. Git is small and lightweight. Large-ish projects just work off of Github, which is fast enough. If the central repository goes down, you have other means (mailing list, etc) for getting back in touch -- granted, GitTorrent would do that for you, but it seems a premature optimization when a central repository works most of the time.

      --
      Don't thank God, thank a doctor!
    7. Re:Why? by Anonymous Coward · · Score: 0

      think much bigger and you will start to see why this is so damn important

      I also am thinking the same thing. But came to different conclusions.

      The problem I see without any sort of 'hosting' is that a project will 'die on the vine' as it were. Many projects are run by 1-5 people. When they loose interest (many do) as for many it is a hobby. What happens to that project? There would be no 'seed nodes' if EVERYONE is a peer. Why would I seed junk I never used and never will, or moved onto something else?

      For example I use CDex to rip my CDs. Yet it is effectively a dead project. With the major contributors bored, or real life, and moved on.

      This works fairly well for 'large' projects where there are a large group of people using it and into it and contributing. But does not fit so well with smaller projects.

      The same problem exists with current torrents. Why would this be any different? Sure it is cool. I will even give it a go when it is up and running. But like all sharing things such as this. As soon as people loose interest the sharing stops. Sometimes *I* am a little late to the party and can not enjoy it because everyone else has moved on.

    8. Re:Why? by SanityInAnarchy · · Score: 1

      the last major upgrade of debian REDLINED the world's internet backbone infrastructure for a WEEK.

      I very much doubt it was the source which caused that issue, or that a distributed git repository would help. I'm guessing it was downloading DVD images, or individual packages -- assuming that this actually happened; I only have your word for it at the moment.

      And the reason it doesn't apply to source code management is, at least technologically, git is damned good -- fast and small enough that it really does not cost very much in the way of hosting. Typically, when I send an update to Github, it's on the order of five kilobytes -- in other words, around a second on a 56k connection. Updates are similar -- maybe ten or twenty kilobytes. Maybe a hundred -- twenty seconds on a 56k connection.

      Having worked with SVN, I can say that while this kind of wait isn't fun, it does work, and it is productive.

      Now, there are ways to use BitTorrent to fetch actual binary packages, but that's a completely separate project.

      i don't _want_ "sponsorship". i don't _want_ my pet project hosted by a large corporation. i want it completely independent.

      Why not?

      they DO NOT have "continuous access to the web site or access to the lovely sponsored hosting".

      I don't see where GitTorrent helps them, though. If they have Internet access, there's plenty of free hosting they can use, particularly for open source projects. If they don't have Internet access, I don't see where a Torrent-like system is going to be any different -- they're still going to have to collaborate locally, probably with GitJour or something similar.

      But see above -- when they are online, just about any definition of being "online' is going to be fast enough for Git.

      --
      Don't thank God, thank a doctor!
    9. Re:Why? by Anonymous Coward · · Score: 0

      Actually, there is work on an open source server software development project for a MMORPG. Unfortunately the company of the MMO has been pursuing legal action against the creators of the private server sources. One kid in Israel was arrested and some developers in Germany are in the beginning stages of legal proceedings. Another received a takedown notice and complied.

      An 'anonymous', distributed source control system would be the greatest method for distribution of the source code. I wish this were further along so that it could be well implemented.. Using a SCM like Subversion as your one and only distribution method is an awful single point of falure, and it has been the downfall of a large number of projects creating servers for this game.

    10. Re:Why? by dkf · · Score: 1

      The problem I see without any sort of 'hosting' is that a project will 'die on the vine' as it were. Many projects are run by 1-5 people. When they loose interest (many do) as for many it is a hobby. What happens to that project? There would be no 'seed nodes' if EVERYONE is a peer. Why would I seed junk I never used and never will, or moved onto something else?

      For open source it really isn't that difficult to find hosting: there are multiple providers out there. Putting everything distributed and P2P won't help very much. What really kills a project though is when nobody cares about it enough to look after it. If nobody cares, maybe it should die. If you care but you're letting it die, it's your fault!

      P2P won't magically make a difference. People, developers, us! We will.

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
    11. Re:Why? by Chandon+Seldon · · Score: 1

      but it seems a premature optimization when a central repository works most of the time.

      Evaluating experimental branches of FOSS projects like that doesn't make a lot of sense. Someone's doing this because they think it's a good idea. Either they're right and they make something great that lots of people use, or they're wrong and they learn something. Like any research, it's awfully hard to tell if it's going to pan out until someone tries it.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    12. Re:Why? by Warthog9 · · Score: 1

      Ok you are so far wrong in your assumptions, assertions and comments it's a bit saddening. Let me set the record straight on where your at right now.

      The primary purpose of peer to peer systems are to either avoid censorship or provide lots of cheap/free bandwidth.

      the primary purposes _now_ are to avoid censorship and to provide lots of cheap/free bandwidth.

      Ok, your partially right here, but in reality P2P in all it's forms is *not* to avoid censorship at all, they are there to provide a mirroring infrastructure where non can or does exist. And BitTorrent is in fact a rather bad mirroring infrastructure at that. Don't try to apply political motives or any other traits to P2P, it's a technical solution to a technical problem (mind you most of the OSS world, and in most everything doesn't actually have this problem and there are a number of papers, reports and findings that are clearly showing the BitTorrent and their ilk do not even remotely compare to the capacity of an even small mirroring system)

      the last major upgrade of debian REDLINED the world's internet backbone infrastructure for a WEEK.

      with the total linux usage only being - what... 1% of the world's desktop systems, and debian being a small fraction of that, the debian mirror system are ALREADY creaking under the load.

      Redlined? Cracking? Debian? I'm sorry to burst your bubble but by the last numbers I have, when Debian releases the internet does not strain under the load. When Fedora releases (currently the largest / most popular Linux distribution at release time) the internet does not load, and it's not uncommon for the Fedora mirroring system to move 100's if not thousands Terabytes in a week. The internet doesn't redline or strain under this load, in reality most people don't even know it's going on. This isn't 1998 anymore, and there are a lot of mirrors out there with 100mbps, 1000mbps and even a few now with 10gbps uplinks to the internet.

      Neither of these really apply to source code management.

      why not?

      Hosting is easily sponsored and the files aren't very big anyway. Few projects will face censorship anywhere other than the most regressive regimes (ie, China or the US).

      i don't _want_ "sponsorship". i don't _want_ my pet project hosted by a large corporation. i want it completely independent.

      This is quite the worthy goal, and I applaud you for it.

      i want my web site content hosted and automatically mirrored across the world, along with its bugs database and its wiki all linked together.

      Here's where your argument falls down though. If you use a traditional mirroring system, yes, your relying on the kindness and sponsorship of others to deal with the distribution of your project.

      How is this any different than P2P? Your now relying on the sheer *kindness* (which in a P2P landscape is not to the pullers advantage) to continue to participate in the P2P cloud. While they are in they are sponsoring you and you are dependent on them. The only way to be truly independent is to run your own mirror on your own system and buy your own bandwidth.

      i want people in the emerging markets and the third world to be able to have exactly the same kind of luxury that we do - and they DO NOT have "continuous access to the web site or access to the lovely sponsored hosting".

      P2P still doesn't really solve that problem. The problem your relating is one of end user's bandwidth vs. bandwidth of a mirror or P2P cloud. If an end user has a small pipe participating in P2P is actually rather detrimental to them as a lot of their traffic will be eaten up trying to participate vs. actually downloading. Slow pipes are also bad for the cloud in general.

      Mirroring here is still a better way to go. G

    13. Re:Why? by MarkRose · · Score: 1

      Redlined? Cracking? Debian? I'm sorry to burst your bubble but by the last numbers I have, when Debian releases the internet does not strain under the load. When Fedora releases (currently the largest / most popular Linux distribution at release time) the internet does not load, and it's not uncommon for the Fedora mirroring system to move 100's if not thousands Terabytes in a week. The internet doesn't redline or strain under this load, in reality most people don't even know it's going on. This isn't 1998 anymore, and there are a lot of mirrors out there with 100mbps, 1000mbps and even a few now with 10gbps uplinks to the internet.

      I run a medium sized forum (25k users) that does 1 TB a month. That's about 4 Mbps, which is not even %0.01 of the available bandwidth into the hosting facility. Even if a Debian upgrade moves PBs, it's not all that much in the grand scheme of things. For what's it's worth, the facility currently moves about 6 Gbps.

      --
      Be relentless!
    14. Re:Why? by Anonymous Coward · · Score: 0

      the last major upgrade of debian REDLINED the world's internet backbone infrastructure for a WEEK.

      Do you have a reference for that? It seems quite unlikely...

    15. Re:Why? by Anonymous Coward · · Score: 0

      Oh please, get a reality check.
      It's nifty, interesting and useful for those that need it but I don't see the world peace nor do I hear celestial choirs coming from it.
      It may be important in your own little world but even the general groupthink of Slashdot disagrees.

    16. Re:Why? by johanatan · · Score: 1

      Don't forget everlasting life.

  7. Not going to change much by LingNoi · · Score: 1

    A website and bandwidth has never been a chokepoint, sourceforge and google code has for years provided bandwidth.

    This is a problem in search of a solution.

    1. Re:Not going to change much by GCsoftware · · Score: 5, Funny

      This is a problem in search of a solution.

      I believe you meant "solution in search of a problem."

    2. Re:Not going to change much by TheRaven64 · · Score: 5, Funny

      If it involves Git and Bittorrent then I suspect it is actually "two problems in search of a problem".

      --
      I am TheRaven on Soylent News
    3. Re:Not going to change much by LingNoi · · Score: 1

      hah, yeah I bummed that up..

      After looking it a little more it sounds like a good concept and I'd be interested to see how it turns out.

      It wouldn't be that useful for projects though since projects rarely fork so there isn't much of a need to have the whole website, forum, etc in git along with it.

    4. Re:Not going to change much by genner · · Score: 0

      This is a problem in search of a solution.

      I believe you meant "solution in search of a problem."

      Why would you want a soultion in search of a problem? He had it right the first time.

    5. Re:Not going to change much by sakonofie · · Score: 2, Interesting
      From http://code.google.com/p/gittorrent/:

      It might currently come across as a solution looking for a problem - and as one smart-ass with admin rights to the Google Code project reminds you on the source tab, "more alpha than the greek letter". The initial motivation was performance of downloads and in particular reducing load on kernel.org.

      Not convinced this is a good idea yet? Oh don't worry it goes on:

      That's one reason d'etre, but to those who argue that is insufficient justification for its existence, that Git is already fast enough - it is a first step towards applying decentralizing Peer to Peer concepts to Git.

      BTW, an excellent way to convince someone a project really doesn't have a "reason d'etre" is insisting it has multiple "reason d'etre"s.

      If you decentralize the download layer, it's just another small step before you decentralize the push rights and tie it to a web of trust such as PGP, and then you don't actually need discrete mirror sites. Every mirror can track the git repositories the owners want it to carry, and those authorized to sign updates can make signed updates to push the cloud forward.

      You had me at performance and distributing bandwidth costs, and probably should have stopped there. Changing ownership of a project from those who control "The Web Site" to those "authorized to sign updates" doesn't do much for me.
      And srly, "central choke-point of control"? As the parent suggested, can't just fork and start a project on source forge or google code?

  8. I still use WANdisco by vinnyjames · · Score: 1

    it keeps everything in sync across multiple locations, provides access control, and works with all my user's existing clients / IDEs.

    1. Re:I still use WANdisco by adiposity · · Score: 1

      How's the speed?

    2. Re:I still use WANdisco by vinnyjames · · Score: 1

      read speeds are almost identical. for writes there is a slight delay to get transactional agreement from a majority of the sites and then the write happens to the local server. the users can't tell the difference.

  9. It amuses me by Reality+Master+201 · · Score: 4, Interesting

    The hyperventilation notwithstanding, what amuses me most is the fact that the project is currently hosted at Google Code.

    Try meditation or something.

    1. Re:It amuses me by lkcl · · Score: 1

      ohmmmmmmmmmmmm

      "i am at onnnne with the universe. i am greeeen!"

      the project was found by accident: the author of the article and the project's authors are not related, in any way.

      think of google code as a bootstrap mechanism: you have to get from here to there _somehow_, and if it wasn't for the old, you'd never get a leg-up into the new....

    2. Re:It amuses me by SanityInAnarchy · · Score: 1

      think of google code as a bootstrap mechanism: you have to get from here to there _somehow_, and if it wasn't for the old, you'd never get a leg-up into the new....

      True enough, but you'd think that you'd start with one of the "old" things which was at least managed with the same SCM your project is for. That is, why wouldn't you use Github for that?

      --
      Don't thank God, thank a doctor!
    3. Re:It amuses me by lkcl · · Score: 1

      i think that google might be a bit peeved if the people who were on that particular GSoC-sponsored project decided that they wanted to use github.org, not code.google.com.... :)

      notwithstanding: even github would be sidelined by gittorrent - or would have to adapt gittorrent...

    4. Re:It amuses me by SanityInAnarchy · · Score: 1

      I'm not sure why this would bother Google -- are all SoC projects required to be on Google Code? For instance, if your project is with the Linux Kernel, would you be required to mirror your subtree, or the entire project, on Google Code?

      --
      Don't thank God, thank a doctor!
  10. if your product is so useful by circletimessquare · · Score: 5, Insightful

    you don't need the hype. linking it to the downfall of vista makes us laugh at you

    just describe what it does, dryly, concisely, technically. if it is worthy of the hype, we will supply the hype for you

    but when you supply the hype, we are inclined to believe there's not much really going on with your project. which might not be true. so change your tone, for your own sake

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:if your product is so useful by lkcl · · Score: 0

      GitTorrent isn't my project. and, if you read the description of the projecton its own, gittorrent looks utterly boring.

      Read the article - which i _did_ write - http://advogato.org/article/994.html - to get an idea of what the absolutely massive implications are.

      whilst many people would be capable of making the same deductions, many people are not.

      so, consequently, i thought it best to spell them out. not least so that other people who are _not_ as technically aware as you or i, who may be just coming in or out of university, can take a look at the list of inter-related projects listed on the original article, and go "cool!"

    2. Re:if your product is so useful by zehaeva · · Score: 1

      oddly enough him using such an archaic word didn't even register in my head, maybe I read too much Shakespeare? ~z

    3. Re:if your product is so useful by ipb · · Score: 1

      "whilst"?

      Seriously?

      Srsly

    4. Re:if your product is so useful by Jamie's+Nightmare · · Score: 3, Insightful

      What you did was take a boring description and dumped in two whopping spoonfuls of hype. As if that wasn't enough, you put a spiteful cherry on top of the Slashdot submission.

      This was my favorite part:

      A government or an organisation decides that it doesn't want free software to be used, as it undermines their ability to exert "control".

      Great. Not only do I have to worry about Chemtrails and controlled demolition conveniently disguised as terrorism, now I learn the government might want to keep me from getting my free copy of KOffice.

      --
      "When you see a unixer brainwashed beyond saving, kick him out of the door." - Xah Lee
    5. Re:if your product is so useful by jeevesbond · · Score: 2, Informative

      'Whilst' is still widely used in the UK.

      --
      I'm going to transform myself into a mighty hawk. Either that or I'll just go and work at Dixons, haven't decided yet.
    6. Re:if your product is so useful by Emb3rz · · Score: 1

      didn't even register in my head, maybe I read too much Shakespeare?

      Same for me, except that it was playing Runescape what did it for me..

      You RSers know what I'm talking about. :)

    7. Re:if your product is so useful by dedazo · · Score: 1

      gittorrent looks utterly boring

      If the project has technical merits, like the GP said, all you need to do is explain what it is. This is Slashdot, not Digg. People will figure out whether or not the hype is deserved.

      The only thing that "rebellion against Vista" bit got you was well-deserved dismissal and ridicule, so you ended up screwing up your valiant effort anyway.

      --
      Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
    8. Re:if your product is so useful by elrous0 · · Score: 1

      Dugg down for not including the requisite flame or "OMG, this is so awesome!"

      Wait, did you say this was /.? Nevermind.

      --
      SJW: Someone who has run out of real oppression, and has to fake it.
    9. Re:if your product is so useful by drsmithy · · Score: 1

      whilst many people would be capable of making the same deductions, many people are not.

      I think the word you're after here is 'paranoia', not "deductions".

      I don't see GitTorrent offering any meaningful advantage. In any managed software project, the "choke point" is the person or person who decides what goes into a given relaese, not anything technical.

    10. Re:if your product is so useful by doti · · Score: 1

      WINE 1.0 is out. Only GNU HURD, a Mac Pro Mini, and Duke Nukem Forever to go !

      You forgot Perl 6.

      --
      factor 966971: 966971
    11. Re:if your product is so useful by Anonymous Coward · · Score: 1, Informative

      What's the problem? "whilst" is a word dickhead.

    12. Re:if your product is so useful by SanityInAnarchy · · Score: 1

      You've supplied plenty of hype, but little substance:

      GitTorrent makes Git truly distributed.

      Git is already truly distributed. What's more distributed about GitTorrent?

      "the web site" no longer becomes the central choke-point of control.

      It's not.

      For a good example, look at the Linux Kernel itself. Yes, kernel.org exists, but it is not a choke point. There are enough mirrors, and enough branches, that some flavor of the kernel will always be available from somewhere, even if kernel.org goes away for awhile.

      Imagine that an entire project - its web site, documentation, wiki, bug-tracker, source code and binaries are all managed and stored in a peer-to-peer distributed git repository.

      Alright. What does that buy?

      To view the web site, you either go to the main site, http://web-site.org/ or, if you are offline or want faster access, you go to the locally checked out copy.

      If we are talking about documentation, most open source projects already include documentation in the repository -- some are generated from the source code itself -- and almost all of it will be installed with the binary package.

      Having a local copy when no Internet access is available is a solved problem. It was a solved problem before Git, and GitTorrent adds nothing to that equation.

      To contribute to the wiki, you either go the main web site, or you edit the local pages and git push them to the cloud.

      First, define "the cloud". No handwaving.

      More relevantly: Again, what does this buy? I can already push to website, if it is a wiki, by editing it directly. If it is not, I can already send contributions back. If they are stored in the repository, that's helpful, too -- but what does GitTorrent itself give me over pure Git?

      To report a bug, you either go to the main web site, or you run your own local web server that duplicates the bug database, and, once you've reported it, the submit ends up with the bugreport being in the locally checked out git repository which, on a push, gets uploaded into the cloud - and ends up on the main web site.

      I would suggest ditz for this purpose, but again, how is this different than pure Git, other than "The Cloud"?

      To upgrade to the latest release, you do a git checkout (of the binaries).

      And why are the binaries being checked into Git? Ever?

      Imagine that you want to fork a project, but you feel intimidated doing so because of the "centralisation". You have no control over the "central web site".

      Check out Github, for that. Each project has a web source viewer, a README, a wiki, and the other things you'd expect (as a software developer) when looking at a project.

      Forking the project can be done by clicking the "fork" button. You now have your own copy of the source, which is pretty much "the website".

      Abandoned projects can easily be revived, through a simple process of a new developer announcing their PGP public key identity, and for Users to start pulling in code that's tagged with that PGP key.

      And how do they announce this? How is this announcement more effective than announcing a new project website and name?

      Users will be able to decide whom to trust based on who contributes, not on who controls the project's web site.

      Already possible. The difference here is, if there's no central website, you're forcing users to go out and learn a version control system, a web-of-trust concept (and make a few trusted friends), and be keenly aware of who is actively contributing and who isn't.

      Versus having a simple, central authority, to the point where I don't even need to find the website; I can just use apt-get.

      In combination with autom

      --
      Don't thank God, thank a doctor!
    13. Re:if your product is so useful by harry666t · · Score: 1

      Well, KOffice maybe not, but [name a few net security tools], [name some strong cryptography software], [name a software package that helps circumventing DRM], or maybe even [name a few distros which focus on security or anonymousness].

  11. The Rebellion Against Vista by Anonymous Coward · · Score: 0

    By rebellion, you mean waiting for whatever MS comes up with next while Linux and Mac get the scraps.

    It may be hard for me to admit, but I'm running 2008 x64 server and I love it. MS will flog the vista code base into a useable desktop before gitwhatever changes anything.

  12. re: by NigelT · · Score: 1, Insightful

    I could see this being used to distribute harmful source code...code that would otherwise violate the terms of service of such sites as sourceforge or Google Code. -- http://nigelt.blog.com/

  13. What exactly have you been smoking? by Anonymous Coward · · Score: 5, Funny

    Coming just in time for that all-encompassing Free Software revolution hinted at by The Rebellion Against Vista

    Can you also point me to where the rainbow-powered unicorn factories are? I imagine they probably exist in the world you seem to live in, you insufferable twit.

    1. Re:What exactly have you been smoking? by Qubit · · Score: 1

      Can you also point me to where the rainbow-powered unicorn factories are?

      They used to be here on Slashdot...

      --

      coding is life /* the rest is */
    2. Re:What exactly have you been smoking? by BotnetZombie · · Score: 1

      Look, I CAME HERE FOR AN ARGUMENT, I'm not going to just stand...!!

      Oh I'm sorry, but this is abuse. Ah yes, you want room 12A, just along the corridor (stupid gittorrent).

      *edited for brevity and exemption from copyright laws

  14. Color me stupid by Enderandrew · · Score: 1

    But a central repository doesn't disappear when seeders disappear, and it is more easily controlled to protect commits. The magic of git is that I can easily have a private branch, and then easily merge it. But is this really a good idea?

    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    1. Re:Color me stupid by lkcl · · Score: 1

      there's nothing to stop an EXISTING site from being the one that publishes their "central" repository via gittorrent. in fact, that's the whole point - initially - of gittorrent: to take the load off the "central" repositories, currently utilising http mirroring.

      but thank you - i will make mention of that, explicitly, in the article.

    2. Re:Color me stupid by Weezul · · Score: 1

      A group of developers can start a private project without central hosting.

      --
      The Christian religion has been and still is the principal enemy of moral progress in the world. -- Bertrand Russell
    3. Re:Color me stupid by tytso · · Score: 2, Informative

      A group of developers can start a private project without central hosting using git already, today. Look at the man page for "git-bundle". Git commits can already be exchaged via e-mail.

  15. Security implications? by zooblethorpe · · Score: 1

    The nice part about a repository hosted on a well-known site is (relative) confidence in the security of the code. If a repo is fully distributed, what's to protect against someone at a node adding malicious code? And, if something malicious is discovered in software you downloaded, how do you track it back to the source node?

    Curious,

    --
    "What in the name of Fats Waller is that?"
    "A four-foot prune."
    1. Re:Security implications? by Sloppy · · Score: 1

      The nice part about a repository hosted on a well-known site is (relative) confidence in the security of the code. If a repo is fully distributed, what's to protect against someone at a node adding malicious code? And, if something malicious is discovered in software you downloaded, how do you track it back to the source node?

      Wasn't that answered in the summary?

      PGP signing (an existing feature of git) and other web-of-trust-based mechanisms will take over from protocols on ports (e.g. ssh) as the access control 'clearing house.'

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    2. Re:Security implications? by TheRaven64 · · Score: 2, Informative

      As mentioned in the summary, PGP. Each branch will be signed with a PGP key, so if you trust the person who owns the key then you trust the code. If someone tampers with it, then they won't be able to sign it. You can still grab their branch, but only if you trust them.

      --
      I am TheRaven on Soylent News
    3. Re:Security implications? by lkcl · · Score: 1
  16. most regressive regimes (ie, China or the US)... by Anonymous Coward · · Score: 0

    sad but true...

    Land of the free... my ass.

  17. Rebellion you say? by Jamie's+Nightmare · · Score: 3, Insightful

    I would rather see a rebellion on Slashdot against articles that announced FOSS news as if it was predicting the second coming of Christ.

    This story is in no way related the the Microsoft's (perceived) loss in market share, not to mention the fact that those who are dropping windows are moving to Apple, not Linux. But hey, gotta go for every low blow you can get while the news is still fresh, right?

    --
    "When you see a unixer brainwashed beyond saving, kick him out of the door." - Xah Lee
    1. Re:Rebellion you say? by lkcl · · Score: 0, Troll

      But hey, gotta go for every low blow you can get while the news is still fresh, right?

      you gotta press those slashdothers' buttons in juuust the right way...

    2. Re:Rebellion you say? by Anonymous Coward · · Score: 0

      Reminds me of someone's sig... "Linux is for those, who hate Windows..."...

      I do not use a software because I hate some other software. I don't even use a software because I love it (because I think it's stupid to love a piece of software, maybe unless you're involved in its development). I use software because it's:

      1. useful for my purpose.

      The fact that >99% of it is free, and 100% of it is not MS has more to do with it being fit to do what I want, rather than with any ideology or zealotry.

  18. Pot calling kettle by Anonymous Coward · · Score: 0

    I bet gittorrent takes over the world before you get that movie finished.

  19. Git over Freenet by togofspookware · · Score: 1

    It's funny that this is at the top of the front page just now. Just a few minutes ago I managed to insert my first Git repository into Freenet (that is, the first Git repo that I have inserted into Freenet, but not my first Git repository). Since git supports cloning and pulling over HTTP, it already supports doing the same thing through FProxy (an HTTP proxy that allows you to browse Freenet's content as if it were regular websites).

    What this doesn't allow you to do is *push* changes to other people's repositories. What you'd need to do in this case is have every developer insert their own git repository into freenet, which others could pull from, and then incorporate into their own repositories. So the accusation that really, truly distributed version control would allow other people to mess up your repositories is hogwash. If someone makes crappy changes, you don't pull from them.

    In case you'd like to try it, the freesite for my program (it's a Ruby implementation of the Freenet Client Protocol, not terribly interesting by itself) is here: freenet:USK@IdWcgxE2jxySYQvAWac4LoGfnU~tGVm7xvRCgvyjp3c,bKLoSHTgen8TW6gQpemdCeh4SKCTwVM~qnOtKZyFY40,AQACAAE/TOGoSFCP/2/ . To git it, you'd just run

    git clone http://localhost:8888/freenet:USK@IdWcgxE2jxySYQvAWac4LoGfnU~tGVm7xvRCgvyjp3c,bKLoSHTgen8TW6gQpemdCeh4SKCTwVM~qnOtKZyFY40,AQACAAE/TOGoSFCP/2/TOGoSFCP.git/

    Of course, you need Freenet installed in order to be able to resolve that URL ~_~

    --
    Duct tape, XML, democracy: Not doing the job? Use more.
    1. Re:Git over Freenet by togofspookware · · Score: 2, Informative

      I forgot to mention that hosting a repository in Freenet actually does have a couple of advantages over having it sit on your (or somewone else's) web server:

      Files in freenet are distributed throughout the network, and persist as long as *someone* on the network still has the file.

      If you are writing a program that government X doesn't like (for kicks, let's say you're living in China and you're developing a 'democracy simulator'), you can host the program in Freenet anonymously - Freenet is designed to make it extremely difficult for anyone to figure out who inserted a particular file, or even on what computers it is being stored.

      Freenet also provides authentication. SSK/USK sites can only be updated by the person who has the insert key. So if you trust the guy that publishes freenet:USK@IdWcgxE2jxySY....nOtKZyFY40,AQACAAE/TOGoSFCP/2/, and you're reasonably sure that nobody else has an insert key, then you can trust that whatever gets put on that Freesite was really put there by him.

      --
      Duct tape, XML, democracy: Not doing the job? Use more.
    2. Re:Git over Freenet by computational+super · · Score: 1
      --
      Proud neuron in the Slashdot hivemind since 2002.
  20. Re:Piracy by Anonymous Coward · · Score: 0

    for example, when ubuntu makes a new release, their servers are usually hit pretty hard, if their servers go down, people can still distribute the iso using bittorrent and the more people that use it the faster it goes

  21. Trademark debacle waiting to happen. by eddy · · Score: 2, Interesting

    BitTorrent Trademark Guidelines: "Misleading or Confusing People. If you are using any of our trademarks in a way that will cause people to get the wrong idea about BitTorrent's involvement in something, you should stop! If you have some reason why you think your proposed use isn't misleading or confusing, let's talk."

    --
    Belief is the currency of delusion.
    1. Re:Trademark debacle waiting to happen. by complete+loony · · Score: 2, Informative

      They've already renamed it MirrorSync and redesigned the entire concept to fit better into the way git repositories already talk to each other.

      --
      09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
  22. What political implications? by MikeRT · · Score: 1

    The only software that provides people with true political power to counterbalance that of others is software that gives them actual power in the political realm. That means software that can take control of resources or kill people and break things. You know what would be a program with political implications? A semi-sentient AI that a rebel group could use to infiltrate its government's command-and-control systems and intelligently make them target their own forces.

    A distributed repository has no political implications that mirroring in general don't have already have.

    1. Re:What political implications? by lkcl · · Score: 1

      A distributed repository has no political implications that mirroring in general don't have already have.

      China. Dubai. internet access is monitored and censored. In Dubai, if a mime-encoded download *happens* to have the letters "sEx" in it, it gets shut off.

    2. Re:What political implications? by richlv · · Score: 1

      darn. they can't read about sussex, england.
      and they can't register at hostels/hotels/conferences where sex has to be specified (this actually happened at my workplace where some admin had set overzealous filters on his own).

      --
      Rich
    3. Re:What political implications? by BlowChunx · · Score: 1

      Dang, man! Are you replying to every single comment? That's quite the astroturfing campaign you are running....

    4. Re:What political implications? by lkcl · · Score: 1

      ha ha :)

      no, not every single one - just the ones that get the wrong end of the stick in some subtle way that could misdirect readers.

  23. Pontiac GitTorrent GTP by Anonymous Coward · · Score: 0

    So is this a new car from Pontiac or something?

  24. No responsibility by Animats · · Score: 1

    This is an iffy idea for data that actually matters. The "torrent" type systems sort of work because they're willing to accept very poor data integrity in exchange for free music and video. Even that's going downhill, as more content shows up with logos, ads, and other various dreck tacked on.

    When it doesn't work, or something gets lost, who do you blame?

    Security is supposed to be through "signing". Who's signing what? Does everybody sign their own check-in, do servers sign collections of files, or what? How do you prevent the insertion of hostile code?

    The problem with "web of trust" systems is that it's too easy to create phony identities on line, who then pretend to trust each other. Like link farms for search engine spamming.

    1. Re:No responsibility by skulgnome · · Score: 1

      What the fuck are you smoking, and where can I find some of that shit?

      BitTorrent has had integrity verification from the very start. In like, 2002. Per-chunk SHA1 hashing. "Very poor data integrity", my eye.

      The signing bit happens like this: you sign the commit object that's at the "tip". This references the log object and the tree object, which in turn references other tree objects and file objects and so forth. All referencing happens via SHA1 hashes, which guarantees as good a level of security as the initial OpenPGP-compatible hash of the tip commit. It's not hard to understand. All hashes can be checked, and the tip commit's signature can be verified using an OpenPGP-compatible tool such as GnuPG.

  25. Hey lkcl by Anonymous Coward · · Score: 0

    Hey lkcl! Having written the last words of the summary did you spontaneously come in your pants?

    Oh, I'm sorry, I've just come.

    1. Re:Hey lkcl by Anonymous Coward · · Score: 0
  26. Re:Surpsise honey! Guess what I stole for you! by togofspookware · · Score: 1

    > Was I close?

    Not so much. Git is a revision control system. The linked-to project is about using BitTorrent to distribute Git repositories. The hype at the end of the summary is unrelated and can be totally ignored. It's not likely that anyone would GitTorrent for distributing movies or non-free software. It'd be possible, but silly.

    --
    Duct tape, XML, democracy: Not doing the job? Use more.
  27. bandwidth and a website in the FIRST world by lkcl · · Score: 2, Insightful

    across most of europe, america and asia, internet access is near-unlimited.

    have you considered the implications of receiving linux on a CD, and being cut off from the rest of the internet?

    how would a group of 100 developers, or 1000 developers, or 10,000 developers - all of them "used to" the current levels of internet access and speed, cope in a situation where the access to the internet was restricted to intermittent 56k dialup?

    1. Re:bandwidth and a website in the FIRST world by SanityInAnarchy · · Score: 1

      In such a situation, I still don't see how GitTorrent helps. I can still use Git over a LAN, manually, and that intermittent 56k is still plenty fast for source-level changes to be distributed via Git.

      --
      Don't thank God, thank a doctor!
    2. Re:bandwidth and a website in the FIRST world by Warthog9 · · Score: 1

      P2P doesn't actually solve a problem for developing worlds either. If an end user has a small pipe they are just going to be spinning their wheels trying to participate in the cloud vs. actually downloading the bits.

      Where P2P actually starts helping is if (1) you have a large pipe at the end point and (2) there is either a choke point between you and your download or at the download it self. If you don't have this *specific* situation P2P is at best no faster or slower than a normal download. At worst, it's dramatically slower.

  28. Isnt that horse dead and stuff?! by Phizzle · · Score: 1

    Cool read up to the bagging on Vista part. Look, its really simple, my Vista PCs work, work fine and are stable, which is a hell of a lot more than I can say about my frigging Ubuntu box and laptop which had choked since 8.04 and forced me to reformat the box to Vista and laptop to BackTrack 3.

    --
    I will not be pushed, filed, stamped, indexed, briefed, debriefed or numbered. My life is my own.
  29. Git already has GPG signing by lkcl · · Score: 1

    read the article: in it, you will see links to the fact that Git already has GPG signing on tags.

    also, you will see references to KeyNote, aka RFC 2704. for convenience, i'm cut/pasting the top bit, here:

    "Trust management, introduced in the PolicyMaker system [BFL96], is a unified approach to specifying and interpreting security policies, credentials, and relationships; it allows direct authorization of security-critical actions. A trust-management system provides standard, general-purpose mechanisms for specifying application security policies and credentials. Trust-management credentials describe a specific delegation of trust and subsume the role of public key certificates; unlike traditional certificates, which bind keys to names, credentials can bind keys directly to the authorization to perform specific tasks."

  30. Re:Surpsise honey! Guess what I stole for you! by pushing-robot · · Score: 2, Interesting

    Not at all.

    Git is a means of sharing and tracking changes to source code for a software project. Formerly, you needed a central server to do that. Now, with GitTorrent, it can be distributed among individual machines.

    GitTorrent is designed to lower the bar for starting a multi-person software project, making it easier and cheaper for developers to collaborate with each other.

    As a side effect, since there's no central server, it will be difficult for an authority to take down or block GitTorrent projects. I suspect GitTorrent will be popular with people developing software that is politically or legally troublesome in their country.

    --
    How can I believe you when you tell me what I don't want to hear?
  31. Re:most regressive regimes (ie, China or the US).. by Anonymous Coward · · Score: 0

    Really?! Your ass is now the land of the free.. Very inspiring. When can I move there?

  32. Re:Piracy by compro01 · · Score: 4, Insightful

    Observe the Ubuntu website this coming April when they release a new version and see if you still feel that a website is appropriate to the task. The site gets hammered so hard that it's problematic to even get the .torrent files directly from them, nevermind the ISOs, and it's not feasible to have that kind of bandwidth sitting around unused except for a few days every 6 months, nor is it currently feasible to get that much bandwidth on-demand for a website, but bittorrent allows for just that, as you're pooling the bandwidth of everyone downloading it. You can easily gets amounts of bandwidth that would cost tens of thousands of dollars to have in a conventional manner.

    --
    upon the advice of my lawyer, i have no sig at this time
  33. Point of Web of Trust by autocracy · · Score: 2, Informative

    You're supposed to have a connection to the "web of trust" system. The system isn't meant to work based on the idea of, "Oh, there are a bunch of keys that have signed each other. Must be fine."

    --
    SIG: HUP
    1. Re:Point of Web of Trust by lkcl · · Score: 1

      look more closely at the way that debian works, paying particular to apt-keyring.

  34. What about persistence? by wealthychef · · Score: 1

    I don't know how this would work with software, as Bit Torrent files seem to have a half-life of sorts, so that older files might disappear. What ensures that the entire list of files expected is actually available, and how do you browse "the repository" for a project?

    --
    Currently hooked on AMP
    1. Re:What about persistence? by lkcl · · Score: 1

      Persistence happens by mistake when people forget to clean out their gittorrent-backed git repositories.

      the nice thing about using gittorrent is that you would end up with copies of the bits of source code and the binaries that YOU were interested in - and, consequently, so would anyone else.

      so, if you were a maintainer of a project, you would be interested in hosting a "central" repository, just like is done now, keeping all the revisions of the software, but it would *happen* to also be _distributed_...

      in many ways, you have to _forget_ what bittorrent is currently used for, and think a bit deeper about what it _can_ be used for...

  35. I want a Choke Point of Control by jdh3.1415 · · Score: 2, Insightful
    This sounds like a nice way to take the load off of the central servers. I don't think it will replace them or make them unnecessary.

    From a technical standpoint, with Git, there's nothing about the central server that is unique. Instead, it's a social convention. Everyone knows where to get the code. Linus discusses this here. http://lwn.net/Articles/246381/

    Perhaps, my imagination is failing; but, I don't think this will change. Most people want to go to a well known trusted place to at least get a secure hash of the code they are downloading.

    For instance, the Debian distro is available via bit torrent. No sane person, downloads the latest Debian .torrent posted by 1337_KeRNeL_haxor on the pirate bay. They get it from debian.com or some other trusted site.

    Also, we really need those central servers. Without them you'll constantly run into distribution problems. Just imagine having to post a message like,"Will someone PLEASE seed the repository. I need to grab the latest kernel."

  36. Debian GPG-signed Web of Trust by lkcl · · Score: 3, Informative

    debian has a keysigning process that creates a web of trust.

    http://www.chaosreigns.com/code/sig2dot/debian.html
    http://www.debian.org/events/keysigning

    1. Re:Debian GPG-signed Web of Trust by Anonymous Coward · · Score: 0

      True, but as a Debian user right now I'm wondering... How do I trust the keys are from DDs? :) I'd have to meet one in person, I guess :)

  37. [Citation Needed] by Rix · · Score: 2, Insightful

    Proof or it didn't happen.

    Why don't you want your pet project hosted by a large corporation? You really just sound like you're whining about nothing.

    I'm pretty sure neither Google Code nor Sourceforge discriminate against the third world.

    1. Re:[Citation Needed] by camperdave · · Score: 1

      I'm pretty sure neither Google Code nor Sourceforge discriminate against the third world.

      But it could easily be the other way around. You could be a third world developer and have a great piece of software to share, say KQuicken for Linux, but you can't reach sourceforge because of your government's firewall.

      --
      When our name is on the back of your car, we're behind you all the way!
    2. Re:[Citation Needed] by MMC+Monster · · Score: 2, Informative

      Is sourceforge firewalled anywhere?

      Also, I didn't know that the backbone was strained by a debian release. Did I miss the /. article, or was that not considered "news for nerds"?

      --
      Help! I'm a slashdot refugee.
    3. Re:[Citation Needed] by Prysorra · · Score: 2, Informative
    4. Re:[Citation Needed] by computational+super · · Score: 1
      Proof or it didn't happen.

      Citation here

      --
      Proud neuron in the Slashdot hivemind since 2002.
    5. Re:[Citation Needed] by sam_vilain · · Score: 1

      They're online services. If you're on the edge of the internet, with lots of local bandwidth but little international, that's not terribly useful.

      --

  38. Doesn't really apply by Rix · · Score: 1

    I don't see why you'd keep a film project in a SCM, and game art assets can be kept separate from the code anyway. SCMs won't track them very well.

    1. Re:Doesn't really apply by grumbel · · Score: 1

      I don't see why you'd keep a film project in a SCM

      For the same reason you keep source in SCM.

      SCMs won't track them very well.

      Centralized SCM do quite fine, Git on the other side does rather horrible since it forces you to checkout the complete history of the project, not so much a problem with text files, but a huge issue with binary blobs, which don't diff well and thus don't compress. A 'git clone' can easily get 10 times as large as a 'svn checkout' for a project with lots of binary stuff.

  39. Re:most regressive regimes (ie, China or the US).. by Anonymous Coward · · Score: 0

    Yep. He gives up his ass freely.

  40. Freak out the RIAA by MarkvW · · Score: 1

    This is a very legitimate torrent use that will frustrate the RIAA in its attempts to stamp out torrents.

    1. Re:Freak out the RIAA by idontgno · · Score: 1

      To a reasonable and informed person, this might constitute a legitimate non-infringing use of P2P.

      To the IP Crusaders, this another step on the slippery slope!

      "Now this evil infringing peer-to-peer technology is being used to host UNSTOPPABLE repositories of COPYRIGHT-INFRINGEMENT and COPYRIGHT-PROTECTION-CIRCUMVENTION software! The P2P terrorists have gone from Torrent as a WMD to Torrent as a WMD factory!"

      I hope /code doesn't get all "all-caps-filter" on me; I'm trying to simulate hysterics.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    2. Re:Freak out the RIAA by Anonymous Coward · · Score: 0

      Next time, try to simulate something a little closer to reality. Much like the submitter, your hyperbole doesn't really serve your cause.

  41. Re: Good point... by hotkey · · Score: 2, Funny

    I could see this being used to distribute harmful source code

    ...for similar reasons, I suggest we make atoms illegal. It is a widely known fact that atoms can be used to make weapons and bombs. I don't understand why the government isn't doing anything about this. Also, I read somewhere that rapists and murderers are made of atoms.

  42. promises to be by baomike · · Score: 1

    right up there with
    proposed
    planned
    we might get to it someday
    we needed something to fill the hole

  43. Overloaded acronyms - GTP by santiagoanders · · Score: 1

    This protocol already exists:

    http://en.wikipedia.org/wiki/GPRS_Tunnelling_Protocol

    Don't make the protocol world more confusing than it already is...

    --
    "There can be little doubt that union activities lead to continuous and progressive inflation." F. A. Hayek
    1. Re:Overloaded acronyms - GTP by smclean · · Score: 1

      Also as the "Go Text Protocol" http://www.lysator.liu.se/~gunnar/gtp/

      --

      "'Yrch!' said Legolas, falling into his own tongue."

  44. Dead project by nniillss · · Score: 5, Informative
    Status, according to the project site, http://code.google.com/p/gittorrent/: Currently no-one is actively developing either this developed version or Jonas' C++ implementation.

    The last project entries/downloads are from February 2008. Why such a hype over a dead/dormant project?

    1. Re:Dead project by lkcl · · Score: 2, Interesting

      because it's the *only* project that links git with a p2p protocol. so, i'm interested in seeing it revived.

    2. Re:Dead project by shutdown+-p+now · · Score: 3, Insightful

      So, how about truthfully saying that in TFA, instead of blathering about the winds of change and the impending revolution?

    3. Re:Dead project by lkcl · · Score: 1

      i'm sorry - that didn't occur to me. it certainly didn't occur to me that a project that has only not had any postings about it for only three months to be "dead".

      plus, the fact that the code exists _at all_ - and is preserved - makes it possible to retrieve and revive it.

      _plus_, if it does the purpose for which it is designed (look at http://htmltmpl.sf.net/ for an example), it doesn't _need_ further work; it doesn't need further "development" - it just "works".

      sadly, though, gittorrent isn't _quite_ finished.
      *shrugs*

    4. Re:Dead project by estarriol · · Score: 1

      Let me get this straight - you *don't* consider your summary to be shamelessly pushing your own agenda? And it didn't occur to you even once that it might be relevant to /.ers that it's a dormant, possibly dead project?

      I realise this site is a soapbox, I just didn't know it was a personal one.

    5. Re:Dead project by Curmudgeonlyoldbloke · · Score: 1

      And the relationship of an SCM system that no-one uses because it isn't finished to "online market share" (which changed largely because more people were at home rather than at work) was what exactly?

    6. Re:Dead project by lkcl · · Score: 1

      i've just heard back from the developers - it's not in the slightest bit a dead or dormant project. the developers are university students. busy and unpaid ones.

  45. (smirk) by circletimessquare · · Score: 1

    "whilst many people would be capable of making the same deductions, many people are not"

    the people who are not making the deductions you are making are the ones who seem to be in better contact with reality

    regardless, no one likes someone else making deductions for them, no matter how truthful

    its patronizing, it drives people away. it demonstrates a colossal arrogance

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  46. Vista rebellion? by Vamman · · Score: 2, Insightful

    You mean someone else supports cleartype fonts now?

    I'm not a Microsoft fan but this shit about a vista rebellion has nothing to do with bringing two technologies together (that also have their warts).

    I'm petty sure the frustrated Vista users won't be benefiting from peer-peer distributed source code anytime soon.

  47. zezima omg by Anonymous Coward · · Score: 0

    Same for me, except tha* ** was playing Runescape what did it for me..

    You RSers know what I'm talking about. :)

    And a famously overactive censor.

  48. Re:Piracy by SanityInAnarchy · · Score: 1

    it's not feasible to have that kind of bandwidth sitting around unused except for a few days every 6 months, nor is it currently feasible to get that much bandwidth on-demand for a website

    Ahem.

    It costs money, yes -- but it's certainly possible.

    --
    Don't thank God, thank a doctor!
  49. Emerging market, Third World and Offline access by lkcl · · Score: 1

    You're used to permanent online Internet access.

    in cases where internet access is prohibitively expensive or even impossible, it makes perfect sense to have everything in easily-syncable git repositories.

    once you have the documentation, the wiki, the code and the bugtracker in repositories, you could even sync those repositories up with the rest of the world through the exchange of floppy disks, CDs or USB memory sticks.

    so the article is about "thinking ahead".

    1. Re:Emerging market, Third World and Offline access by vrmlguy · · Score: 1

      You're used to permanent online Internet access.

      in cases where internet access is prohibitively expensive or even impossible, it makes perfect sense to have everything in easily-syncable git repositories.

      You missed a few scenarios.

      --
      Nothing for 6-digit uids?
    2. Re:Emerging market, Third World and Offline access by pjt33 · · Score: 1

      But why is a P2P component necessary? Git already allows distributed development, so the only scenario in which there's a real gain is when someone else on the same LAN as you has a checkout of the repository you want, but you didn't realise that. Is this likely?

  50. The essential question by Anonymous Coward · · Score: 0

    So we can put porn on Git, right?

  51. DeCSS by Anonymous Coward · · Score: 0

    Ooh a new way to distribute DeCSS source!

  52. Re:Piracy by Opportunist · · Score: 1

    Define illegal. Distributing documents that certain organisations (or, say, religions...) don't want to see distributed? Showing video footage that certain governments would love to see vanish (because, say, it shows how they deal with protesters)?

    But don't worry, governments will agree with you and make this tool illegal for that very reason. Or national security. Or any other excuse if the price is right.

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  53. ambitious project by jyro1980 · · Score: 1

    I had attempted an implementation of similar concept limited to Java applications and based on top of JXTA P2P protocol as my MS project. http://www-users.cs.umn.edu/~salvi/downloads/jyro_aos_project.doc All the possible applications mentioned in this article are nice and are known for a long time. What matters is execution. Good luck to the project!

  54. Could this be used for things other than code? by lennier · · Score: 1

    Git is basically just a generic distributed versioning-filesystem layer, right? Source control is its current killer app, but it's got no particular hooks to make it dependent on that domain.

    So if we combined Git + Bittorrent... does that give us a generalised peer-to-peer distributed filesystem?

    If so, that's a whole lot more interesting than just a way to share source code fast. Imagine a true peer-to-peer Web built on something like this.

    Imagine, for instance, posting blog or wiki posts as little paragraphs of text, each as a separate file, not uploaded to a 'server' but just put out onto the grid. Cache every chunk of data as it moves through servers, maybe have a name-resolution layer like DNS over the top so that one server is 'authoritative' for your blog posts, but that server doesn't need to be online all the time as long as another one has replicated the data. Add a language which allows transclusion of chunks and/or functional manipulation of them, so you don't have to use messy AJAX tricks which bust the caches.

    We could get a few steps closer toward Xanadu.

    --
    You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    1. Re:Could this be used for things other than code? by lkcl · · Score: 1

      Git is basically just a generic distributed versioning-filesystem layer, right?

      yep.

      Source control is its current killer app, but it's got no particular hooks to make it dependent on that domain.

      nope.

      So if we combined Git + Bittorrent... does that give us a generalised peer-to-peer distributed filesystem?

      yep!

      If so, that's a whole lot more interesting than just a way to share source code fast.

      oh yeahhhh :) e.g. GitFS - http://www.sfgoth.com/~mitch/linux/gitfs/

      Imagine a true peer-to-peer Web built on something like this.

      Imagine, for instance, posting blog or wiki posts as little paragraphs of text, each as a separate file, not uploaded to a 'server' but just put out onto the grid. Cache every chunk of data as it moves through servers, maybe have a name-resolution layer like DNS over the top so that one server is 'authoritative' for your blog posts, but that server doesn't need to be online all the time as long as another one has replicated the data. Add a language which allows transclusion of chunks and/or functional manipulation of them, so you don't have to use messy AJAX tricks which bust the caches.

      We could get a few steps closer toward Xanadu.

      hey, can you ghost-write my next article on this subject, for me? :)

  55. Re:I want a Choke Point of Control by Weezul · · Score: 1

    GitTorrent seems more about keeping everyone's repository updated. No one will ever accept you're pushed content if you're not on the inside. You can still contribute but only through the more slow traditional vetting process of emailing a repository update along with change explanations.

    What is mega different is that two ego tripping developers can stop pulling one another's changes while allowing other developers to continue pushing to everyone.

    --
    The Christian religion has been and still is the principal enemy of moral progress in the world. -- Bertrand Russell
  56. I call bullshit... by jnareb · · Score: 2, Informative

    I call bullshit and gross exagerration. First, GitTorrent lacks any implementation, there is only some code testing concepts in the GTP 0.1, the draft of protocol. Second, Git is distributed version control system by itself, and doesn't need GitTorrent for this: GitTorrent is meant only to distribute the load of initial clone and fetching large parts of history among peers (among clients), reducing load on the server it clones from; no more.

  57. In British English by scatters · · Score: 1

    git - Noun:
    Brit slang a contemptible person [from get (in the sense: to beget, hence a bastard, fool)]

    Do we really need a torrent that facilitates easy distribution of these people?

    --
    A One that isn't cold, is scarcely a One at all.
    1. Re:In British English by booch · · Score: 1

      Actually, Linus named it after himself:

      I'm an egotistical ***, and I name all my projects after myself. First 'Linux', now 'git'.

      See the git FAQ.

      --
      Software sucks. Open Source sucks less.
  58. Big Binaries: I hate them by hachete · · Score: 2, Insightful

    Given that a fair proportion of most of the firms I've worked for do not know how to use SCMS, a lot of the SCMS I've maintained contain rather large binary snapshots. Also, distributed firms. So this might be a useful tool if I could get people to use it. Which is unlikely.

    but the politics? In this case, leave it out. Just a distraction.

    --
    Patriotism is a virtue of the vicious
  59. Re:Piracy by Farmer+Pete · · Score: 1

    I'm not saying that Ubuntu would foot the bill, I'm talking about having centralized torrent hosting sites for... legit content! Who'd have thunk it? There are other, easier ways to get the desired outcome without creating a safe haven for piracy, which is obviously what this is about more than anything else.

  60. Er... by Rix · · Score: 1

    You keep source code in an SCM to manage diffs. Binary blobs don't diff very well.

    Sure, it makes sense to keep binary blobs intended for specific revisions in an SCM, but other than that?

    1. Re:Er... by grumbel · · Score: 1

      A SCM in the most basic sense is for recording past versions of a file and you want that for your data just as you want it for text. Diffing and merging is more difficult with binary, but not impossible, especially when done manually. In the most basic sense you simply want to know if and when a file has changed and that works for binary just fine.

      On a more practical level when you have multiple developers you also want to track who modified which file and of course give people access to a shared repository, a SCM does exactly that, a plain file storage would be much more problematic.

  61. Freemanic Paracusia by hoytak · · Score: 1
    --
    Does having a witty signature really indicate normality?
  62. It's a dead project, Jim. by Anonymous Coward · · Score: 0
    C'mon, dude. Let's run it down:
    1. No postings for three months. NONE. Admitted by you.
    2. The code is parked, or as you said, "preserved" ... you even follow that with "retrieve and revive it."
    3. You close with "it isn't quite finished."

    In the words of the bards, "This. Is. A. Dead. Parrot."

  63. Been there with CVSup by NuShrike · · Score: 1

    We welcome our Git brothers for reinventing the wheel again versus CVS's established http://www.cvsup.org/ for mirroring and distribution.

    The more the merrier.

  64. Re:Piracy by compro01 · · Score: 1

    Which then leads to the problem of how to effectively filter for "legit content" or even how to define what "legit content" is.

    --
    upon the advice of my lawyer, i have no sig at this time
  65. My solution is very different by syousef · · Score: 2, Funny

    I always check my GIT repository into SVN for safe keeping ;-)

    --
    These posts express my own personal views, not those of my employer
  66. Distributed Name space management DROP DNS by kentsin · · Score: 1

    Instead of sign DNS, why dont we just maintain the dns by ourself?

    Allow a distributed dns may get better security. the dns is just a assistant way to make address easier to use. It shall not be a reaon that the net have a single central control and a break point.

    It is the site to give out ip as well as the preference name, it is the user to decide how to call the ip.

    It is the freedom.

  67. "Giterdone?" by Anonymous Coward · · Score: 0

    Attention, whoever tagged this "giterdone": I hate you.

  68. Distributed git an old idea... by jgarzik · · Score: 1

    This idea has been around since 2005 at least...

  69. So do you actually do this? Professionally? by Rix · · Score: 1

    I'm genuinely curious.

    It seems to me that there'd be better revision management tools for video.

  70. A torrent of Gits? by Anonymous Coward · · Score: 0

    Sounds like most nerd conventions.

    "Git: A completely ignorant, childish person with no manners; a person who feels justified in their callow behaviour."

    http://www.urbandictionary.com/define.php?term=git

  71. awesome... distributed porn... video... audio... by advocate_one · · Score: 1

    and anything else you want... just set up a distributed git repository for it...

    --
    Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
  72. Re:I want a Choke Point of Control by jonaskoelker · · Score: 1

    For instance, the Debian distro is available via bit torrent. No sane person, downloads the latest Debian .torrent posted by 1337_KeRNeL_haxor on the pirate bay. They get it from debian.com or some other trusted site.

    Have a look at debtorrent (or apt-p2p)...

    You're right that you need centralized servers for signatures, and a backup seed if no one else seeds. But other than that, it's safe to grab binaries from just about anyone.

    Unless you think that either the crypto doesn't work, or it's been misapplied. In that case, the trust you need if you download from a centralized server is that there are no men in the middle.

  73. Oh boy, 4chan/b/ in a gittorrent by Anonymous Coward · · Score: 0

    Oh noes! The glasses they do no good!

  74. Re:I want a Choke Point of Control by harry666t · · Score: 1

    > No sane person, downloads the latest Debian .torrent
    > posted by 1337_KeRNeL_haxor on the pirate bay.

    The code would be all signed. If you trust the keys, you can trust the .torrent. You can't trust debian.org to provide you with "good" torrents if it won't provide the signatures along, or can you?

    > "Will someone PLEASE seed the repository. I need to grab the latest kernel."

    Yup, I can imagine this happening. But rather for +5 year old archives. And even then, I'm pretty sure there would always be a few bastards that'd keep the 0.99 releases of Linux, pre-1.1 Debian, etc. We'd just move away from thinking of projectname.org as a source of stable, central... "authority"? -- and just grab everything from the closest neighbor (which _could_ be debian.org), and verify the signatures.

  75. Re:Surpsise honey! Guess what I stole for you! by VE3MTM · · Score: 1

    You never needed a central server for Git. You've always been able to do "peer-to-peer" distributed development by transferring patches over email, or by setting up a git daemon.

    --
    09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 Whoops, silly middle mouse button...