The New Improvements of uTorrent 2.0 (Final)

Oh, I see. I did misunderstand you, then. But what you're mentioning about uTorrent is actually a good thing - torrenting traffic will automatically adjust its speeds depending on what the rest of your programs are doing. Meaning you can max out your upload without making surfing lag, for example, even if you haven't limited your upload speed. And when you aren't doing anything else with your PC, the client will know this and maximize uploading.

To give a rough example, say you're seeding a full speed without uTP and want to check your e-mail or browse this forum. They should load very slowly, because your connection works like a "pipe" - lots of upload going one way prevents your download from coming fast. In this case you'd reduce your upload speed limit as you send your mail or read the new threads, and put it back how it was before when you're done. uTP does exactly the same thing, just transparently.

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?

Maybe so, but the impact shouldn't be noticeable unless you have a very slow upload speed or another application is claiming most of it - and I think you should stop your torrents if you're going to use your upload for something else in the first place.

"uTP has been improved significantly since 1.8.5, with many bugs fixed and performance improvements."

source: http://forum.utorrent.com/viewtopic.php?id=65482

so it may be a much different UTP than what has been there sine UT 1.8.

You have a point there, but looking at the changelog it's mostly bugfixes and performance improvements. Until someone shows actual proof the new uTP favors high-speed peers, I won't believe it.
 
AdrianPhoto, pro267 is right regarding DHT being a client-side protocol in the sense the tracker as we know it isn't involved. :) (Technically, every DHT node is a tracker, but that's outside the scope of this discussion)

Regarding the MPAA call-homes, you can find info in the first pages of this thread, or by doing a simple Google search.
 
Personally I'll stick with 1.8.2 in case some of the rumoured issues are fixed and until it's whitelisted everywhere. There are very few reasons to keep a client as stable as uTorrent up to date when you're simply adding more bugs to the mix.
 
UT2 has to many flaws for for private trackers,great for public types
UTP seems to favor seed to it own and other clients are lucky to connect to it.This for the fairness of sharing and keeping a ratio on a private site will cause issues.Isp will love this client as it will be able to traffic bandwidth if need in high end isp loads.
Big thumbs down for me
 
UTP seems to favor seed to it own and other clients are lucky to connect to it.This for the fairness of sharing and keeping a ratio on a private site will cause issues.

Someone quoted a BitMeTV announcement stating the same in my board - care to show some evidence of that?
 
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.

i'm using uT 1.8.5. Can you (or anyone) give me specific instructions how to make these tweaks (or provide a link where i can learn about this), please.

Here's what i don't understand:

1) I know how to use a hex editor. What are the specific things that need to be removed from the exe?

2)
a)What are the IP ranges for router.utorrent.com and router.bittorrent.com?
b)If I knew them, can I just plug them into a custom peerblock list?

3)
a)What's the purpose of the dht.dat file? and
b)why do you need to get one from a friend?

4) Do you have to do both of these methods, or would one suffice?

thanks
 
God help us with all those uT fanboys.

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, then seeing how the uT dev team reps denied it until the (same) BT community forced them to admit it.
 
Someone quoted a BitMeTV announcement stating the same in my board - care to show some evidence of that?

Come on anon-sbi this could be good for you, instead of utorrent add on's(won't be need) going to be a great need to other client add on's to boast their share rate.Sure you are firon haven't teamed up :lol:
 
Using a hex-editor is easy. It's like Notepad, but deeper. You can find a good one here:
http://mh-nexus.de/en/hxd/
Note the official uTorrent EXEs are compressed with UPX, so you'll need to download the "uncompressed" builds or unpack them yourself using UPX or QUnpack before you can edit them.



I remove the following things in my mods:
Code:
239.192.152.143
239.255.255.250
http://www.utorrent.com/report_problem.php
http://update.utorrent.com/checkupdate.php
http://update.utorrent.com/updatestats.php
llsw.download3.utorrent.com
ll.download3.utorrent.com
http://update.utorrent.com/installstats.php
http://download.utorrent.com/offers/tb_ask-1.5.1.0.exe
http://%s/offers/tb_ask-1.5.1.0.exe
http://download.yandex.ru/yandex-pack/utorrent/YandexPackSetup.exe
http://download.yandex.ru/yandex-pack/utorrent/YandexPackSetup-utorrent-20090724.exe
http://search.utorrent.com/search.php?q=%U&e=%U&u=1

You can replace the IPs with 000.000.000.000, and simply fill the rest with null bytes.

2)
a)What are the IP ranges for router.utorrent.com and router.bittorrent.com?
b)If I knew them, can I just plug them into a custom peerblock list?

a. both use the same IPs: 67.215.242.138, 67.215.242.139
b. yes, you can add them to your PeerBlock blocklist and they should no longer be contacted.

3)
a)What's the purpose of the dht.dat file? and
b)why do you need to get one from a friend?

a. the dht.dat file contains the addresses of other peers uTorrent will connect to to form part of the DHT after start-up.
b. the "router.*.com" hosts give you some peers to get you started when you've just installed uTorrent. If you're a bit paranoid, you'll block them, but then you'll be unable to bootstrap (connect) until you get your hands on a dht.dat file - so I recommend asking a friend for his. If your DHT is already working, there's nothing to worry about.

4) Do you have to do both of these methods, or would one suffice?

If you're paranoid, you should do both :lol: Personally, I only block the call-homes and don't touch the "router.*.com" addresses. But then again my country is outside the MPAA's reach for the time being.
 
causing the client to secretly report all your torrent activity to them, then seeing how the uT dev team reps denied it until the (same) BT community forced them to admit it.

lol, please give us a link where that happened. exactly, you're just making up stuff and spreading FUD now...
 
lol, please give us a link where that happened. exactly, you're just making up stuff and spreading FUD now...

That was the case but the mpaa contract is over pretty sure it was a one year deal could be wrong

http://libcom.org/forums/news/utorrent-bought-mpaa

http://gigaom.com/2006/12/12/utorrent-users-upset-over-bittorrent-deal/

Plenty of articles about it

Far as reporting stuff back to mpaa that was not true tests were taken out no leaking data

What was true was utorrent scare tactic's to get everyone to update from there 1.6 and 1.6.1 builds to 1.7.7 and 1.8.* builds, by telling us that there was a exploit in those builds was not true.
 
aha.

"Announcement: Using uTorrent 2.0+ This is a preliminary warning to all our members, who are currently using, or are thinking about switching to uTorrent 2.0 or later. 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, giving users of that client what is considered to be an unfair advantage in seeding. A somewhat similar behavior by another client, BitComet, in the past, had resulted in that client being banned from pretty much every private site in existence.

Communication between representatives of the BT community and the uTorrent development team is undergoing, however at this stage the problem was not resolved yet. As a result, multiple private sites have already banned this client, and many others are likely to follow in the very near future. We are one of the sites who are seriously considering banning usage of this client.

With this announcement, we would like to both inform our members about this possible outcome, encourage those who haven't upgraded yet to refrain from doing so for now, and strongly recommend to those who have already upgraded to downgrade to earlier versions...."

announcement at some tracker
Trackers are going to start discriminating because some people have an unfair advantage in seeding over others. Good one.
 
Back
Top