Slashdot Mirror


Today in P2P

Hylton Jolliffe writes "I wanted to alert you to an article by research Marc Eisenstadt that digs deep into BitTorrent, its potential and limitations and its implications for podcasting, filesharing and more."

8 of 135 comments (clear)

  1. Re:/.ed already? by jacobcaz · · Score: 5, Informative

    GET REAL
    January 11, 2005
    BitTorrent, eXeem, Meta-Torrent, Podcasting: "What? So What?"
    Posted by Marc Eisenstadt

    SUMMARY: The index that facilitates the sharing of files on a large scale is also the Achilles heel of peer-to-peer file-sharing, because it is vulnerable to litigation and closure. So what happens if the index is itself distributed? I try to get my head around the latest in peer-to-peer file sharing, and explain a bit about what I've learned, including the fact that BitTorrent's power rests in its 'swarm' distribution model, but not necessarily in your end-user download speed. What has this got to do with podcasting? (Answer: invisible P2P plumbing helps the podcasting wheel go round).

    [Warning: lengthy article follows].

    First, some history
    (skip ahead to the next section if you're already bored with the Napster, Gnutella, KaZaa, and BitTorrent saga).

    Napster opened our eyes to the power of distributed file sharing on a massive scale. But it was closed down by lawsuits to stop it from listing copyrighted works for which the owners would naturally have preferred to collect royalties (there are thousands of commentaries on the pros and cons of such royalties, but that's not the focus of this posting). Successive generations of tools such as Gnutella, KaZaa, and now BitTorrent have created their own buzz, their own massive followings, their own headaches, and their own solutions to others' headaches. Here's my rundown of the 'big ideas' (and the people behind them):

    Napster (Shawn Fanning): This was the Mother of big-time peer-to-peer (P2P) file transfers, i.e. my computer directly to yours, with a central server to maintain lists of who had what in order to initiate the transactions. It had a pretty decent user interface, plus the rapid growth, novelty, excitement and publicity that ensured plenty of good content. Those central server lists, leading to mass free trading of copyrighted material, also led it to be shut down.

    Gnutella (Justin Frankel and Tom Pepper, creators of WinAmp): This was an open-source protocol that linked autonomous 'nodes' (users of the network) to other nodes, thereby eliminating the need for a central server list. Searching reliability varies, however, because it is subject to outages according to the connection/disconnection of individual users along the way.

    KaZaa (Niklas Zennstrom and Janus Friis, who later created Skype): This technology built on a proprietary protocol called 'FastTrack', conceptually an extension to Gnutella, that deployed distributed 'supernode' search indices whose IP addresses were built in to the software, and which avoided the problems of (i) Napster's centralized lists and (ii) Gnutella's over-distributed nodes suffering outages and weakening the search. The prevalence of built-in 'adware' and the distribution of 'junk files' that masqueraded as originals were two of the weaknesses of the (still) wildly popular KaZaa.

    BitTorrent (Bram Cohen): This was the next 'creative leap' in the P2P world, based on the following insight: distributing large files in fragments among large numbers of users, and requiring every downloader to be a partial uploader (of these fragments), enables the 'best of breed' of swarming behaviour -- as a file becomes more popular, so it becomes easier to download, rather than harder (as is the case with traditional file distribution)! A good overview explanation and a helpful analogy are provided in this excerpt from Brian Dessent's BitTorrent FAQ and Guide:

    BitTorrent is a protocol designed for transferring files. It is peer-to-peer in nature, as users connect to each other directly to send and receive portions of the file. However, there is a central server (called a tracker) which coordinates the action of all such peers. The tracker only manages connections, it does not have any knowledge of the contents of the files being distributed, and therefore a large number of users can be supported with relatively limited tracker bandwidth. The key philosophy

  2. Article Text by LanMan04 · · Score: 1, Informative

    January 11, 2005
    BitTorrent, eXeem, Meta-Torrent, Podcasting: "What? So What?"Email This EntryPrint This Entry
    Posted by Marc Eisenstadt

    SUMMARY: The index that facilitates the sharing of files on a large scale is also the Achilles heel of peer-to-peer file-sharing, because it is vulnerable to litigation and closure. So what happens if the index is itself distributed? I try to get my head around the latest in peer-to-peer file sharing, and explain a bit about what I've learned, including the fact that BitTorrent's power rests in its 'swarm' distribution model, but not necessarily in your end-user download speed. What has this got to do with podcasting? (Answer: invisible P2P plumbing helps the podcasting wheel go round).

    [Warning: lengthy article follows].

    First, some history
    (skip ahead to the next section if you're already bored with the Napster, Gnutella, KaZaa, and BitTorrent saga).

    Napster opened our eyes to the power of distributed file sharing on a massive scale. But it was closed down by lawsuits to stop it from listing copyrighted works for which the owners would naturally have preferred to collect royalties (there are thousands of commentaries on the pros and cons of such royalties, but that's not the focus of this posting). Successive generations of tools such as Gnutella, KaZaa, and now BitTorrent have created their own buzz, their own massive followings, their own headaches, and their own solutions to others' headaches. Here's my rundown of the 'big ideas' (and the people behind them):

    Napster (Shawn Fanning): This was the Mother of big-time peer-to-peer (P2P) file transfers, i.e. my computer directly to yours, with a central server to maintain lists of who had what in order to initiate the transactions. It had a pretty decent user interface, plus the rapid growth, novelty, excitement and publicity that ensured plenty of good content. Those central server lists, leading to mass free trading of copyrighted material, also led it to be shut down.

    Gnutella (Justin Frankel and Tom Pepper, creators of WinAmp): This was an open-source protocol that linked autonomous 'nodes' (users of the network) to other nodes, thereby eliminating the need for a central server list. Searching reliability varies, however, because it is subject to outages according to the connection/disconnection of individual users along the way.

    KaZaa (Niklas Zennstrom and Janus Friis, who later created Skype): This technology built on a proprietary protocol called 'FastTrack', conceptually an extension to Gnutella, that deployed distributed 'supernode' search indices whose IP addresses were built in to the software, and which avoided the problems of (i) Napster's centralized lists and (ii) Gnutella's over-distributed nodes suffering outages and weakening the search. The prevalence of built-in 'adware' and the distribution of 'junk files' that masqueraded as originals were two of the weaknesses of the (still) wildly popular KaZaa.

    BitTorrent (Bram Cohen): This was the next 'creative leap' in the P2P world, based on the following insight: distributing large files in fragments among large numbers of users, and requiring every downloader to be a partial uploader (of these fragments), enables the 'best of breed' of swarming behaviour -- as a file becomes more popular, so it becomes easier to download, rather than harder (as is the case with traditional file distribution)! A good overview explanation and a helpful analogy are provided in this excerpt from Brian Dessent's BitTorrent FAQ and Guide:

    BitTorrent is a protocol designed for transferring files. It is peer-to-peer in nature, as users connect to each other directly to send and receive portions of the file. However, there is a central server (called a tracker) which coordinates the action of all such peers. The tracker only manages connections, it does not have any knowledge of the contents of the files being distributed, and therefore a large number of users can be supported with relatively limited tracker band

    --
    With the first link, the chain is forged.
  3. Re:Another useless blog by froggero1 · · Score: 3, Informative
    eMule? What's that?

    I use aMule

    --
    ~/.sig: No such file or directory
  4. Karma whore by narsiman · · Score: 2, Informative
  5. Re:Legal uses by ari_j · · Score: 4, Informative

    Just a suggestion - try 'ABC', as in 'Yet Another Bittorrent Client'. It is a far better Win32 client than is the official python client.

    That being said, I agree that Bittorrent needs to be publicized more for its clearly legal uses. I won't say that all multimedia downloading is illegal copyright infringement, but even under the assumption that it is, Bittorrent is still the single best way I know of for widespread legal distribution of large files.

  6. Re:So? by UlfGabe · · Score: 2, Informative

    Remember how Exeem is made by Slotnick, who is employed by an unknown suit....! Using exeem you really dont know what you are getting, it could be the *AA's or anything, so dont trust it until the sponsoring partner comes out in the open. ps. exeem is like eMule..... so use eMule/eDonkey -blah-

    --
    Check journal for info on Anti-TextBook, an idea by me.
  7. Re:Another useless blog by Caseyscrib · · Score: 2, Informative

    If you don't like the stories posted by Michael why don't you just uncheck his name from the authors list on your profile's homepage tab settings. Then his stories will never appear for you again.