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."
"There are two issues people need to come to grips with," BitTorrent CEO Ashwin Narvin told Slyck.com. "The genie is back in the bottle, and the cat is back in the bag."
Sorry, I just thought that was funny. If you RTFA, though, it sounds like the sky isn't falling just yet. The client, which was closed source before, is still free (as in free beer), and the protocol is available to anyone who asks for it.
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.
Video Production Support
.. the moment Bit Torrent was commercialised and started playing with the big TV guys this was bound to happen. I'm just surprised it took so long.
Malicious software re-packaging is a lame excuse too.
What's the name going to be for the upcoming auto-encrypted open-sourced fork of Bittorrent?
Ryan Fenton
Wouldn't it be great if someone could create some kind of license that allowed free access to the source code, but provided grounds to sue malicious companies that attempted to take that code and include it in closed source proprietary products without giving anything back to the community!
Oh, wait...
Affect them? Hardly at all. Let's face it, other teams have grabbed the ball and are running with it. The official Bit Torrent folks are going to have to work to stay at all relevant, "premier reference implementations" aside.
The higher the technology, the sharper that two-edged sword.
So I wonder how long it will be before the source is out on the Pirate Bay...
Try to hack my 31337 firewall!
I'm a bit confused by this. Isn't this what licenses are for? Why not just sue the people selling and profiting from your open source product for breaking the license? It just seems to me that the reasoning doesn't make much sense. There are plenty of examples of people selling closed source software that's "free" to people who don't know any better(like Kazaa) and are less tight-fisted with their money than I am. It seems to me that decisions like this don't scare off someone someone who wants to resell your program to make a buck, doesn't help someone so incurious as to not wonder if there is a free version of the software they are being asked to buy, but does hurt the person who just wants the source for their own reasons. Am I wrong?
The company that owns the BitTorrent trademark is not the arbiter of the protocol or anything else. Do they even own that trademark?
Note that they opposed the addition of encryption, and they were completely ignored. BitTorrent, the company, is entirely irrelevant.
Does anyone "know" how it will impact other clients? No, we don't "know" that, however, a reasonable estimate would be "not much, if at all."
utorrent may be the single most popular BT client as TFA claims (OTOH, most of the peers I see are Azureus and Ktorrent. I don't know if that's just because I'm in the odd niche of only doing legal stuff over BT (no, it exists, really Linux and *BSD ISOs), or if most people are using those, I don't know.
Either way, what I expect will happen if they go totally closed will be much like what happened with SSH. After the official SSH became closed and proprietary, the OpenSSH project picked up where they had left off, and while SSH is still in business and has a product line, OpenSSH took over the market and is now far more popular, on both the client side and the server. If BT totally closes everything off and makes the protocol incompatible with open versions, I think we can reasonably expect to see the open source version fork and take over the BT market.
"Welcome to obscurity, gentlemen. We hope you enjoy your stay. To ease your transition, we've assigned a personal guide for the both of you. Heidi, please call Mr. Fanning and let him know his group is here."
Please stand clear of the doors, por favor mantenganse alejado de las puertas
Hm, it seems to be referring to UPnP (which I have vehemently disabled on my router).. but I wonder if they have any idea what they're talking about. If you can't accept incoming connections that just means that your client initiates all transfers of data, not that you're completely incapable of uploading. Good clients like utorrent (and apparently not Bittorrent 6.0) will give/trade data without being asked if there's available upload bandwidth. Not the best for efficiency (though I should think it'd at least volunteer less-available data first) but it gets you a high ratio nonetheless.
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.
The problem being that when one company has near monopoly, and in the eye of the public is indistinguishable from the product, they can close source, then change the specs (even if the spec is published), and the open source alternatives won't be able to compete.
This is partially because they'll always play catch-up, and partially because they won't be able to improve the specs themselves -- if they do, they'll become incompatible, and crushed by the product everyone uses.
Example of just this effect: RTF, which Microsoft bought back in 1990. Open source RTF readers are usually several versions behind, and anyone expecting to read RTF documents no matter what version have to use the latest Microsoft products to do so. This is not what the situation was like back when RTF was still open (despite being proprietary), and DEC let anyone see the coming changes.
And that's the best case scenario. The worst case scenario is if they close the specs too. That, of course, will kill them in the end, but in the mean time it's going to cause lots of grief.
This is very off-topic, but, about your sig: The last time I clicked on a .cx link on Slashdot was a long time ago, and it's going to be a long time until I do it again...
The GPL cannot keep the original author from changing the license and closing the source nor can it prevent the protocol from being closed either.
The only thing it can do is keep that source (the version that was under the GPL) available to the open-source community. Which, btw, can be accomplished by any other open-source license. Btw, they have already done this.
Basically, we're in the exact same situation now that we would have been if it was GPL'd.
That my fellow community developers will take this opportunity to drop the BitTorrent protocol. Time to develop something better.
It's time we address it's critical failure... that you can see which IP's are trafficking in which files. There has to be an obscure way in which people can just exchange data blobs. Where the blobs are interleaved or multiplexed with data of other files and you don't know and can't know with all practicality what a particular blob contains until you finally collect enough blobs to reconstruct your data file. There are more blobs to be collected for a particular file for data redundancy but you only need to collect so many of them to recreate the data set. Meanwhile sure you downloaded more data then you needed to for that particular file but all the blobs you downloaded are still in demand from other people because of their relevance to other data sets. And you can safely continute to server those files because you don't necessarily know what multiplexed data they contain. Blobs also mutate and remix over time as to which combined data they contain.
There's a trap waiting to happen.
If they merge uTorrent (non-free, closed) with the older "BitTorrent 5.0" (open source, free), hell's going to break lose if there's any GPLed patches in the open source that Bram didn't make.
GPL applies to even "lowly" patchers and debuggers code, as it does to the 10klines per day guys.. (joke)
Im ready for a torrent of gpl-violations
While we're at it, let's point out how wonderful some of those tags are.
This story is tagged "lame" and "bastards" among other things. So yeah, if I'm interested in looking up info on OSS software being closed, I'll be sure to look for articles tagged "lame". That imediately makes so much sense to me, and you guys clearly know what good tagging's all about. Tagging's a great way of expressing opinions on entire stories without having to own up to them. You don't even have to have to LEAVE A FUCKING COMMENT WITH A USER NAME.
C'mon, at least post AC, dickheads.
I don't therefore I'm not.
It wasn't about clients that leech bandwidth, it was about clients with great interfaces, and additional management methods, such as uTorrent or Azureus' web management. In my opinion, the mainline client was so lacking in features that I considered it to be unusable. Bittorrent owes some of it's success to the fact that there are so many great clients for people to choose. If you're looking for simple, try uTorrent or Transmission. If you need advanced features, try Azureus. People like this kind of choice. It saddens me to see this, as it means that clients might eventually become less compatible with closed-source revisions of the protocol, and we'll lose some great file-sharing software.
Unlike porn, which yada yada rimshot hey-ooh!
It's a pity they're going closed source, but it wouldn't be unfair for Blizzard to toss a few gold pieces back their way given all the money Blizzard is making.
Talk about closing the gate after the source has bolted!
Sorry about that. Truly, deeply sorry.
This guy probably thinks that computers are just for porn and that college is just for drinking.
They aren't??? It's not???
/. zen: Imagine a Beowulf cluster of Beowulf clusters...
Where can I find the .ryanfenton for the latest Heroes episode!!?!?111@!!
> Q: How will this impact the BitTorrent open source development community as a whole?
A: Once word gets out about our RIAA backdoor, Azureus is going to kick our ass. Ummm... you better not print that.
Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
KTorrent is my favorite pure torrent app on any platform, with utorrent running a close second. Both are very fast, light-weight clients.
I've also dabbled with mldonkey and shareaza as more multi-purpose p2p apps that also support torrents.
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
People use Bittorrent -- or more specifically, many people use uTorrent -- to connect to public BT trackers and to other people running similar client programs. Bittorrent (the company) doesn't control either. In fact, I don't think that Bittorrent-the-company's "reference implementation" is particularly popular for trackers, and they're really where the marketshare matters.
I don't think that the majority of bittorent (the protocol) users are just going to bend over and throw away the software that they've liked, just because Bittorrent (the company) decides it would be cool to produce a new, ad-laden, DRM-using, Hollywood-mogul-approved version of their software, that breaks compatibility with older versions. In fact, I strongly suspect that the trackers which drive the more popular torrent aggregation sites would refuse to recognize such a "broken" implementation, and would instead favor free implementations (old versions of uTorrent, Azureus, etc.).
What's happening here is that Bittorrent (the company) has become fully decoupled from bittorrent (the protocol). They have very little leverage over the latter; about all they have is the rights to the name "Bittorrent," and the 'reference implementation,' which won't be worth its weight in electrons once they start messing with it.
The comparisons to Microsoft and RTF aren't really apt, because Microsoft had a way they could easily control the format -- they just made future versions of Word produce output that was incompatible with other vendors' software. But Bittorrent can't really do that, because a bittorrent client is only useful insofar as it can communicate with the swarm. As long as the trackers that drive the most popular torrents (which, let's face it, are the illegal ones; warez and movies) don't start using the new/broken protocols, it seems unlikely that a broken protocol would gain traction.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
And that's only skimming your description.
Besides, not being able to preview files will pretty much make it useless for anything mainstream. Like pirating crap. So, if this protocol is never used for piracy, it will never need such insane protection from the MAFIAA because it will never blip on their radar. Oh, it can be used for other things, like downloading Linux ISOs? BT already does that. Secure file transfer? LOL Traffic analysis foiling? Tor. What else?
You are coming to a sad realization: Cancel or Allow?
Do not attribute to malice that which can be easily explained by incompetence.
Did they just say that the issue with open source was people taking the source code and doing there own thing with it? I thought that was the whole point of it.
Im a gamer, not a grammer major. This post is full of spelling and grammer mistakes.
It'll be just like when SSH Inc. closed SSH. Guess what - SSH Inc's ssh implementation is no longer the reference implementation - instead, OpenSSH has become the reference implementation. BitTorrent Inc. can say they are the reference implementation as often as they like but it won't make it true - instead, an open BitTorrent implementation will probably become the reference, and just like SSH Inc. BitTorrent Inc. will fade towards irrelevance (although they may continue to exist).
Oolite: Elite-like game. For Mac, Linux and Windows
Seems like this'll only split the bittorrent protocol, there's a fairly wide variety of clients out there and the only thing that held them together was the official protocol. Azureus has been making small breaks even with the official protocol around, so now it'll probably split. The question is which client will the other ones follow, now that BitTorrent have given up their niche in true XFree86 style.
// MD_Update(&m,buf,j);
I gotta say, as clunky as Azureus has been, they've obviously been working hard on the thing, because it works so much more smoothly now. Even with a few torrents running, I don't get huge CPU grabs like I used to, and the overall feel of speed is definitely improved.
Linux, you magnificent bastard, I read the fucking manual!
uTorrent is so lightweight that I've left it running in the background and downloaded After Effects and Premiere without noticing.