The New Improvements of uTorrent 2.0 (Final)

I like uTorrent for many things, call me fanboy or whatever

causing the client to secretly report all your torrent activity to them
Would you be please tell me the Version and the Build so I can test it..
Now let's see who's gonna run..

Edit: Btw, the deal was announced "December 7, 2006", so that would be between 1.5 - 1.7
 
The dev team at utorrent.com has proclaimed the release of a new final uTorrent 2.0 version. It is the first stable (non-RC, non-beta) release from the time of uTorrent v2.0 development which began again in August. The most popular BitTorrent client in the world has suffered some important changes; including UDP tracker support & auto-uTP, transfer cap settings, an enhanced setup guide, new shiny skin and bandwidth management.

do5eg5.png


 
The least you could do is cite the source when you copy and paste something :dry:

Source:

http://extratorrent.com/article/245/the+new+improvements+of+utorrent+2+final.html

Also, One thing I was curious of:

I remember reading this article here: http://filesharingtalk.com/vb3/f-ne...nate-the-need-for-isp-throttling-375275/page2 , and in many places UT 2.0 was very poorly received for the many connotations that there would be heavy throttling to accommodate this new fangled "uTP" feature. However, it seems like that has mostly subdued now. Did they change something or alter their plan from what was originally said in that article? I haven't upgraded yet for this reason.
 
All this uT crap started back at 1.6.1
I also faced it as a scare tactic to force upgrades to the newer versions.
As I read on the webz, there was a lot of coliding views on those same nasty rumours, so I couldn't be arsed and moved on to Vuze until today.

It is heavy, but it easily has more features than any other client I know of.
Utorrent 2.0 isn't seducing me yet, so let's wait until the dust settles to make a valid opinion.
 
Also, One thing I was curious of:

I remember reading this article here: http://filesharingtalk.com/vb3/f-ne...nate-the-need-for-isp-throttling-375275/page2 , and in many places UT 2.0 was very poorly received for the many connotations that there would be heavy throttling to accommodate this new fangled "uTP" feature. However, it seems like that has mostly subdued now.

TCP traffic is easy to inspect and throttle accordingly because due to its "safe" nature, shaping devices can clearly see when a connection is initiated, the handshake, and "take it from there".

UDP, in turn, is unreliable - you simply start throwing data to the remote host and hope he'll receive it correctly, because there's no error control at the protocol level. (Although it works fine in practice, actually) ISPs can't throttle uTP without also affecting all other UDP network traffic (VoIP, online gaming, etc.). Nobody will want to pay for a provider that won't even let you talk or play games.
 
It looks like the development team of uTorrent has implemented a new feature into the 2.0 client that is considered "unethical" by us, as well as many other BT sites. This feature causes uT 2.0 to prefer uT 2.0 over any other client out there

"It looks"? Meaning they aren't even sure what they're saying is true? :huh:
 
I wonder whether they would still be such fanboys if they knew about uT history, specifically the callback function the uT dev team has added to uT a couple of years ago (after they were bought by a company associated with the MPAA), causing the client to secretly report all your torrent activity to them

It's easy to remove them (or at least most of them) by unpacking the executable and using a hex-editor. so I'm still using it :P
 
That transfer cap could be extremely useful for all other fellow comcast users.

I'm going to cap my torrent machine at 200gb a month so they don't shut down my service lol.
I usually just keep track by keeping rough estimates. I have been doing most of my seeding off my seedbox recently anyway though...
 
I can see this going three ways,
1). Some Sites will ban UT2 and allow and encourage earlier models of Utorrent to 1.6
2).Others more likely the bigger sites will allow UT2 and put pressure on other clients to update to UTP or risk banning their clients.
3).Others will allow,who gives a fook allow everything we not here to shape BT future we are here for the cash ;)

Could be a number 4--if we had a coder we'd have a allowed list

Time will tell.
 
As I read on the webz, there was a lot of coliding views on those same nasty rumours, so I couldn't be arsed and moved on to Vuze until today.

It is heavy, but it easily has more features than any other client I know of.

Took the easy exit, huh :lol:

But I agree. Vuze is a great, very tweakable client. And while it's not a feather like uTorrent when it comes to resource usage, you won't feel it's there with enough RAM and a decent processor.
 
I like uTorrent for many things, call me fanboy or whatever

Would you be please tell me the Version and the Build so I can test it..
Now let's see who's gonna run..

Edit: Btw, the deal was announced "December 7, 2006", so that would be between 1.5 - 1.7

1.7.7 was the first release that the mpaa venture with utorrent was built and didn't phone home any packets.Nor did the 1.8.# builds.

This still was a very dark time in utorrent history,
with many peeps opting for other clients.It was a pity such clients as Halite didn't step up as utorrent would have lost a lot more peeps.

anon-sbi proof of the new ut2 build favoring its own will come to light when uppers when you see ut2 being the upper(only seeder) on a box it will give to other ut2 clients others clients will find it hard to connect to the seeder and other ut2 peers.
Not sure how to give you your proof, but get someone to connect on a linux box rtorrent or transmission under those conditions and see how you go.
 
I'm not exactly sure if you understood my post, but I meant throttling from utorrent's side, not the ISP's.

Here was a quote from the article that made many others (and me) wary of this new version:

With uTP, uTorrent (and the Mainline client) will become network aware by throttling itself if congestion in the network is detected. This will have a huge impact on ISP networks according to Simon Morris, BitTorrent’s VP of Product Management. “If uTP is successful it should result in a multi-billion dollar windfall in terms of savings for ISPs,” Morris told TorrentFreak

This means that the new uTorrent will eliminate the need for ISPs to throttle BitTorrent traffic in their networks. Of course, uTorrent users will also be affected by the new protocol. When needed, uTorrent will decrease the upload or download speed to avoid congestion.

According to Morris it’s mainly the upload speed that will be affected. “The throttling that matters most is actually not so much the download but rather the upload – as bandwidth is normally much lower UP than DOWN, the up-link will almost always get congested before the down-link does,” he explained.

Have these issues been addressed in someway that decreased the uproar over 2.0? I don't really see anyone complaining about this anymore.

And as a side note, Morris mentions that it's "only the upload" that will be affected. If the upload is throttled, doesn't that ultimately lead to slower download speeds as well?
 
If you don't know how DHT works, then please.. for the love of every god men ever believed in.. Don't write just to sound like you know.
:glagpinch:

let's look at this:

1- Private tracker, you're safe! DHT disabled
2- Public tracker, your IP & Info hash for files you're downloading are distributed anyway, on any version of uTorrent or any other BitTorrent client.

I suggest reading this
http://wiki.theory.org/BitTorrentDraftDHTProtocol
First, let me answer the claims:

1. No, you're not safe in a private tracker; that's another misconception of people who have no idea what they're talking about. Now, if you would've actually known what you were talking about, you would know that DHT is a client-side protocol that has nothing to do with the tracker being private or not.

The only thing private sites can do is turn on the private flag in torrent files and count on the clients to respect that by turning off DHT, peer exchange and local peer discovery. Once they do, it's totally up to the client to respect (or not) that flag. In fact, the uT version I've specified above did NOT respect the private flag and multicasted info hashes to organization-local addresses. By the way, another client (BitComet) was banned from various private sites for disregarding the privacy bit.

2. While info is available for harvesting on public trackers, it is not fed with a spoon to the MPAA.

Oh, and since you were nice enough to comment on my knowledge of the subject, may I suggest that in the future, you actually try to read that DHT draft before posting mindless spam..
router.utorrent.com and router.bittorrent.com? Those servers deliver some DHT nodes for you to bootstrap after installing. If concerned, just block those IPs and ask a friend for his dht.dat file.
That's one possible solution for people who know about this issue. Most people are not aware of it.
 
Agreed. Halite is the great, fast and lightweight client no one seems to use. :wacko:

anon-sbi proof of the new ut2 build favoring its own will come to light when uppers when you see ut2 being the upper(only seeder) on a box it will give to other ut2 clients others clients will find it hard to connect to the seeder and other ut2 peers.
Not sure how to give you your proof, but get someone to connect on a linux box rtorrent or transmission under those conditions and see how you go.

If you have access to a seedbox running uT 2.0 I guess you could send me an screenshot of a peerlist when uTorrent favors others of its kind. Of course, to be 100% sure I'd need to check it out myself, and I don't have a box :P
 
Back
Top