The Uncertain Future of BitTorrent
javipas writes "The people behind the popular BitTorrent tracker are working on a new version of the BitTorrent protocol that could become the successor to the current one, maintained by BitTorrent Inc. The company founded by Bram Cohen — original author of this protocol — now has decided to close the source for several new features in the BitTorrent protocol, and this "gives them too much power and influence". The new file format would be called .p2p, and would maintain backwards compatibility with current .torrent files."
Let them close it. As long as the open source community doesn't use it to distribute isos, I'm happy.
You can give OSS to the people, but you can't take it back!!
Perhaps that's one of the biggest reasons people should think long and hard about attempting leverage open source to gain popularity and a user base. There's that possibility of the user base forking your work and taking it over if they don't like the direction you're going... and that's exactly what I predict will happen with BitTorrent. And while they're at it, they'll probably go ahead and build into it some anonymity protection.
from the standards-are-hard dept.
Apparently Taco finds that basic grammar are too hard, too.
And because of those closed features, the new tracking system will probably not be as popular because no one likes to use the original bittorrent client. That is until they reverse engineer it. Anyone who torrents anything (legal or otherwise) will notice there are like no original bt clients showing up. Why is that? Could it be it sucks? Unless these new features are like gold, no one will care and will continue to use the old one.
Just keep using the existing protocol. You might miss out on the latest K-Fed release if all the kiddies are using the new format, but then again that could be a plus.
Are these new "features" that need the source to be closed RIAA or NSA oriented ?
I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
The PirateBay team is currently developing on a new torrent protocol that they hope will be the next-generation successor to the current BitTorrent file. They say that they're concerned about continuing to use the current standard since BitTorrent has closed the source and hope to be able to create an open-source successor that maintains backward-compatibility with the current .torrent standard. The new standard, currently named .p2p is still in the development phase, but the initial release is planned for sometime early next year. Among the planned new features are responses to the increasing number of spammers and anti-piracy organizations who currently abuse the BitTorrent protocol.
Seriously, would it have been that hard to have waited for a submission that was informative and grammatically correct?
There are some very interesting technologies that can be applied to a new .p2p format while remaining backward-compatible with .torrent files. Such as auto-regeneration of almost-complete torrents via in-file redundancy (small size increase, massive benefit), the possibility of onion routing and obfuscation, new uploading algorithms, that sort of thing.
.torrent specifications -- the old, open one and the new, partially-closed one -- why not go whole hog and fork the thing all to hell? An application should be able to easily handle both.
And honestly, if Bittorrent closes some of the protocol, the features either going to be ignored or reverse engineered. In which case there's already 2 different
[ think ]
they is. and our children is learning.
We know, and believe me, you will be the first against the wall when The Revolution comes.
The creator of this post (Jacob Smith) hereby releases it, and all of his other posts, into the public domain.
DRM? Adware? I don't see why it needs to be closed unless it's stuff people don't want.
After MPAA got Bram Cohen and the UTorrent guy on their pockets, it was a matter of time until they tried to pull such stunts. My bet is that they will try to close a "hole" in the protocol, the impossibility to create a truly private swarm, one where only authorized peers could connect, regardless of the desire of the peers themselves to share the information about the other peers (DHT style). That's the wet dream of people selling content, they could sell access to their content using the bittorrent protocol and nobody would be able to join the swarm without paying.
But there is nothing there people should be afraid., as everybody knows, real innovation on the P2P scene occurs when the interested parts (the filesharers, not necessarily illegal ones) are the real force behind the development, as PEX (protocol encryption) came to prove, now that the cat is out of the sack, there is not a lot of things that Mr. Cohen can do.
If a person wants to illegally share music, they could (hypothetically) get a pair of 300GB USB drives. Put all their music on them. Go to the library, check-out more music. Put that on their drives. Go to their friends houses and trade. A couple of trades with friends who are actively trading will:
1. quickly net them more music than they can listen to in an entire lifetime.
2. make sure they have off-site backup of their music in case their house is burned down by RIAA goons.
And, if you don't put it on-line, none of it is traceable by RIAA. And Comcast can't stop it.
So? It's going the same path of Overnet and so many others. Closed source = failure. Let them die alone.
And they speak as if they were the only ones who could develop new features. Don't forget about the distributed network for BitTorrent and all the good things clients and servers have implemented to improve existing protocols, BitTorrent and others.
I was about to say 13256278887989457651018865901401704640, but it appears this number is private property.
By keeping the source closed, he is in fact assuming all responsibility for the actions of his code. If his code allows something bad to happen, we can say with certainty that it's all his fault.
Obviously a lack of seaders is preventing the spread of good righting.
http://thepiratebay.org/search/oxford%20english%20dictionary/0/3/0
Long live the Ryan Fenton protocol!
When you want random-access to a file, streaming doesn't work. That's why BitTorrent is so good. Also, it means you can publish your own content and not have to send it to everyone, just some folks. Once it's out there, if it's popular, other folks can download it from others, saving you thousands in bandwidth costs. FLV is just a video codec - it's being served over HTTP, which is ages-old and not particularly suited for mass-dissemination of data in a bandwidth-effective way, anyway. FLV might be good for low-quality videos, but it sure ain't good for gigs of ISOs, DVD-quality movies, albums, libraries of pictures, etc. It's all about using the right tool for the job, and FLV is great at streaming low-quality videos to users at great expense to the server.
Hmm. You must be new here...
Hmmm.
I dont want to be paranoid, but...
RIAA/MPAA/**AA are trying to legislate against P2P
They have several key bitTorrent devs in their pockets
They are promoting a new *better* protocol
How long before this is a negotiating tools to the powers that that control the legislation - on the lines of "yes, P2P has legitimate uses, but the new protocol will safeguard those interests whilst protecting copyright" or something on those lines. In other words this could be an initial step towards the long term goal of a legal P2P system that is easy to police/control content. These people plan a long way ahead, I would not be surprised if something like this is brewing...
Mind you I like the concept of packet obfuscation to thwart ISP throttling mentioned in TFA.
If his code allows something bad to happen, we can say with certainty that it's all his fault.
Manufacturers do not assume liability if their product is used to perform illegal activities. How long would Heckler and Koch, Gerber, and Ronson remain in business if they were held liable for every knife fight, gun duel, and arson?
When our name is on the back of your car, we're behind you all the way!
what ever happened to Freenet? I know it had totally different objectives than BitTorrent, but it was interesting nontheless.
Hey Pirate Bay folks, here's my list of feature requests for the new version of your open source torrent protocol:
ONION ROUTING:
1) Implement Onion routing (aka: Tor / anonymize the sources) as a built in feature.
2) Onion Routing should, where possible, try to use exit points and middle points that have roughly the same amount of bandwidth as you, otherwise torrenting will not become a reality through Onion Routing. So some kind of peer bandwidth algorythm needs to be incorporated.
3) Onion routing should be on by default, and each user should also become an exit point and donate 30% of their bandwidth to this. This will greatly increase the number of exit routers & provide this as a defacto alternative, as opposed to just some obscure security feature for the 31337 (hackers & government homeland types).
4) Individual site upload ratios, should take into consideration that fact that you are an exit point and some portion of that 30% should be counted toward your uploaded bytes ratio (even if traffic is going to other sites)... in other words, help promote torrent security = get bonus points from private trackers.
SIMPLIFY ISP SHAPING BYPASS
Background: Forcing protocol encryption isn't enough these days; some ISPs are shaping or even blocking torrent traffic by methods such as sending TCP RST packets to close a session, or their infrastructure auto-analyzes your encrypted traffic patters and if they are high bandwidth, very encrypted and on for long amounts of time to the same destination you get flagged & shapped (regardless of the fact that you could indeed be doing something legal)
1) There's a page on Wikipedia that lists all the "BAD ISPs" (http://www.azureuswiki.com/index.php/Bad_ISPs). This is a list of ISPs internationally that in one way or another shape your bitorrent traffic (Comcast anyone?). We need to be one step ahead of these ISPs and render their multi-million dollars worth of shaping infrastructure useless - sooner rather than later - sooner so that they can't make up for the ROI on all that gear they purchased. If the ROI fails, the next time engineering dept approach CEO for X dozens of millions more, they will get declined and we (torrent community) will win.
2) This site breaks down "throttling" into 5 different categories or ways in which the ISP can throttle you... each listing the bypass method.
http://www.azureuswiki.com/index.php/Avoid_traffic_shaping#Escalation_of_the_crypto_settings
Note that level 5 (the most aggressive shaping method known so far) is only bypassable by a single client today (Azeurus), utorrent to my understanding can not bypass this.
Anyway my point with these above 2 items is that these facts need to be considered:
1. The number of ISPs throttling internationally is already large and growing larger
2. Your new torrent client needs to simplify bypassing these various levels of encryption so that it can be adopted by the masses. If it is not adopted by the masses (rendering ISP throttling useless), the ISPs will have won.
I don't have time to type more, so please research what other clients out there (beyond just torrent) are doing and borrow ideas from them.
Here's a brief list of intelligent encryption/anonymous software out there to investigate:
RODI: http://slashdot.org/article.pl?sid=05/06/01/1252232
MUTE: http://mute-net.sourceforge.net/
ANTS: http://antsp2p.sourceforge.net/
GNUnet: http://gnunet.org/
I2P: http://www.i2p.net/
FreeNet: http://freenetproject.org/
TOR: http://tor.eff.org/
THanks and good luck!
No trees were killed in the making of this post; however, many trillions of electrons were horribly inconvenienced.
Okay, let's assume the almost-done is not caused by malicious junk torrents, and instead just that nobody has the last part. Presumably then, it's because everybody who did have it left.
So, if there was 1% overhead that went into parity... those people would just leave 1% sooner (since they can regenerate the files they need anyway). So everybody would be stuck at 98% and still unable to use the parity. That won't be helpful.
Parity is useful in newsgroups because your servers won't randomly run away from you when they're done, it's just lossy in a random fashion. For bittorrent, you're reliant on whoever's seeding to stick around.
Another poster has opined that Freenet is dead, with just a few users and almost no content. That mirrors my experience. Yet you seem knowledgeable and still include a link to it. Do you know something I don't? I'm serious about this; I'd really love Freenet to work. AFAIK, though, it just doesn't in any meaningful way.
If your experience is different, please take a moment to elaborate.
If *anyone* has any current, positive experience with Freenet, please jump in. I figure *somebody* is probably still using the thing. I'm just wondering who, why, and if they're actually getting anything done.
Which similarly never killed anyone, although some of the more famous stations DID broadcast from ships in international waters...
Remember "News for Nerds, Stuff that Matters"? Help make it a reality again! http://soylentnews.org
They should call it... .arr
--Won't that be grand? Computers and the programs will start thinking and the people will stop. - Dr. Walter Gibbs
Do you know something I don't?
;-)
Aw, poor Alice! She's so clueless and disappointed because she hasn't found Wonderland... yet
Yes, Alice, I do know something you don't. Freenet is for posting stuff, but there are OTHER similar (anonymous) networks around... some haven't made it to the public, and some are still in beta (but already working imho). They implement onion routing, and are very secure. Some are used for file transfer, others for general purpose (to host websites, forums, etc). Yes, they work.
Just search for the rabbit hole (hint: Steganographed text inside), Alice. Just keep it secret until the time comes.
but am I the only one that read the article and asked why there is such a huge focus on avoiding litigation?
Disclaimer: I use bit torrent to download files regularly, which may or may not be copyrighted. Take what I say here with a grain of salt. Also, this is not meant to be a trolling post.
From the article:
Before I get to my real point, I want to call bullshit on this. People don't upload out of a fear of litigation (at least that is not their entire motive), they don't upload because they're a bunch of leaches who don't want to share their own bandwidth. Anyway, on my real purpose here.Seriously, come on. I think it's great that there is an interest in improving the BT protocol, but I think the motive for it needs to be examined. Any improvements that might be implemented should be in the spirit of making it easier share content within the legal framework. The focus should not be to avoid litigation, or to bypass network traffic shaping, or anything else along those lines, it should be solely to improve the ability of users to share legitimate content. Politics should have no role in the development of the protocol whatsoever.
The fact that litigation and network traffic shaping has been taken into consideration indicates that there is something wrong with the current copyright system, and that is really what should be addressed here. By taking the BT protocol and adding these kind of features the p2p community is putting itself in direct conflict with the 'AAs. This is only going to add more fuel to the fire, and it will give the 'AAs more ammunition. They will be able to point to the specs for the new protocol and say it was designed with the intent of illegally distributing copyrighted material, and they will be right.
God, schmod. I want my monkey man!
You can't take the sky from me...
Wait a minute, that link has a search string at the end! Someone call Amazon!
Could not open
I guess it's better'n pullin' some sword out of a lake.
PiratFS :D
You're missing the point. Keeping ISPs from eavesdropping on bittorrent is nice, but that only saves you from throttling and forged RST packets, not lawsuits.
Assuming the pirated song is in a public torrent, MediaSentry can and join the swarm and start requesting chunks of data. If their client can connect to my client and download chunks of whatever file they're "protecting" today, I'm equally hosed whether those chunks are coming from a file stored on my hard drive or forwarded from someone five layers down in the onion. End-to-end encryption doesn't help when the attacker controls an endpoint.
(The former AC, now home from work)
0 1 - just my two bits
In that case, just call it the FSM.
And instead of .torrent, files will have an .appendage extension.
Arrrr!
Ignore this signature. By order.