Slashdot Mirror


BitTorrent Closes Source Code

An anonymous reader writes ""There are two issues people need to come to grips with," BitTorrent CEO Ashwin Narvin told Slyck.com. "Developers who produce open source products will often have their product repackaged and redistributed by businesses with malicious intent. They repackage the software with spyware or charge for the product. We often receive phone calls from people who complain they have paid for the BitTorrent client." As for the protocol itself, that too is closed, but is available by obtaining an SDK license."

5 of 390 comments (clear)

  1. Not RTFA? Read this at least. by tonsofpcs · · Score: 5, Informative

    So basically BitTorrent bought uTorrent and is staying closed source (as uTorrent is now). Q: How will this impact the BitTorrent open source development community as a whole? A: There will be no impact to the BitTorrent open source development community. We are committed to maintaining the preeminent reference implementation of BitTorrent under an open source license. Although the latest documentations won't be published for the world to see, an aspiring BitTorrent developer or a hardened coder can still obtain the specifications on the latest protocol extensions by obtaining a SDK license.

    1. Re:Not RTFA? Read this at least. by PaintyThePirate · · Score: 5, Informative

      Not exactly. The only mention of an SDK on the Bittorrent site is part of a "device certification program", that would undoubtedly involve paying Bittorrent in exchange for licensing their now proprietary information and some offical seal of approval. There is no mention of open source projects being able to see/use any changes in the protocol. Luckily, I assume that most bittorrent trackers (public or private), will ban any incompatible official client if the protocol does change, rather than adopting the official client and abandoning all of the others.

  2. Re:In related news... by Anonymous Coward · · Score: 5, Informative

    And uTorrent belongs to Bittorrent(company) and always has been closed source.

  3. rtorrent pwnz by Anonymous Coward · · Score: 5, Informative

    get rtorrent
    http://libtorrent.rakshasa.no/

    with adsl2+ i could get >1meg/s with hundreds of connections, totally stable and only used around ~1%cpu time on a p3 933.

    use gentoo and -O3 it too.

  4. Re:It was only a matter of time.. by kripkenstein · · Score: 5, Informative

    One difference. They don't operate any of the servers people actually use. Unless they can convice the server operators (most of whom they can't legally even admit exists, which will make negotiations somewhat awkward) to adopt their closed protocol, who will notice any optional dead protocols their 'official' but little used client supports?
    No, that isn't quite true.

    First, Bittorrent is a peer-to-peer protocol. Only a minor part of it is communication with the server (aka tracker). They might keep the tracker protocol exactly the same, and alter the important p2p part.

    Second, this has already been done, and successfully. For example, utorrent came out with a 'PEX' (Peer Exchange) protocol that wasn't in the spec. So it was only used between peers that were both using the utorrent client. This provided a nicer bittorrent experience for utorrent users, especially as utorrent's marketshare rose. Later on, because of utorrent's dominant position, other clients started to implement utorrent PEX (KTorrent, libtorrent-based clients), with varying degrees of success.

    A similar issue is Azureus's DHT protocol, which is not in the standard. Although at least Azureus is open source, so you can read the actual code to help in understanding what nonstandard protocols they have invented (but then they also have a very nice wiki).

    The point is, it is easy to 'embrace and extend' the bittorrent protocol, even if you don't have control of the servers. Is 'extinguish' next? Probably not, but I for one won't be using the official Bittorrent client.