bottlerockets Posted April 5, 2014 Report Share Posted April 5, 2014 It has come to my attention that the latest 3.4.1 stable, beta, and nightly releases all use the same -UT341- peer identification string, which makes it difficult for torrent sites which use a client whitelist to allow the stable releases while still prohibiting the use of beta or alpha torrent clients on their tracker. Some may choose to not allow 3.4.1 at all because of this, which causes problems for users who automatically update their client or assume that new versions will always be allowed. May I suggest going back to the format with -UT3410-, -UT341B- and -UT341A- prefixes for stable, beta and alpha releases?Not sure if it's related, but it seems like the first character after the version prefix is always %00, and the user agent in 3.4.1 contains some weird number like (109148100). Link to comment Share on other sites More sharing options...
askewfilm Posted April 7, 2014 Report Share Posted April 7, 2014 It has come to my attention that the latest 3.4.1 stable, beta, and nightly releases all use the same -UT341- peer identification string, which makes it difficult for torrent sites which use a client whitelist to allow the stable releases while still prohibiting the use of beta or alpha torrent clients on their tracker. Some may choose to not allow 3.4.1 at all because of this, which causes problems for users who automatically update their client or assume that new versions will always be allowed. May I suggest going back to the format with -UT3410-, -UT341B- and -UT341A- prefixes for stable, beta and alpha releases?Not sure if it's related, but it seems like the first character after the version prefix is always %00, and the user agent in 3.4.1 contains some weird number like (109148100). I have an issue with this as well. A tracker that I use will not add stable version 3.4.1 to the whitelist because the new beta version has the same identification string as do the new "minimally tested and unsupported" nightly builds. Hence, if they added the stable release, they would be adding the beta and alpha versions at the same time. I do not want to downgrade to 3.3.2. Is there any chance these identification strings can be changed on the beta and alpha versions? Please reply, thanks Link to comment Share on other sites More sharing options...
djbluntmagic Posted April 8, 2014 Report Share Posted April 8, 2014 This issue needs to be addressed - it's a major obstacle to adoption of this update, has already been causing headaches with the userbase, and quite frankly is a bad and nonsensical policy. Link to comment Share on other sites More sharing options...
secretmethod70 Posted April 10, 2014 Report Share Posted April 10, 2014 Yes, please fix this! Link to comment Share on other sites More sharing options...
fuzzywuzzzy Posted April 12, 2014 Report Share Posted April 12, 2014 This would be very helpful. Link to comment Share on other sites More sharing options...
Zulithe Posted April 13, 2014 Report Share Posted April 13, 2014 This needs to happen. Thanks. Link to comment Share on other sites More sharing options...
bottlerockets Posted April 15, 2014 Author Report Share Posted April 15, 2014 Hey, are you guys ever going to address this issue? For all the hubbub made in another thread about how tracker staff "never" contact you about bugs, you sure like to ignore the issues that -are- reported. This shouldn't even be a difficult thing to fix, and it would be an immense help. Thanks. Link to comment Share on other sites More sharing options...
DreadWingKnight Posted April 15, 2014 Report Share Posted April 15, 2014 Are you exclusively looking at the Peer ID, or are you also looking at the user agent being reported? Link to comment Share on other sites More sharing options...
bottlerockets Posted April 15, 2014 Author Report Share Posted April 15, 2014 Peer ID only. Ocelot (tracker software) does not do anything with the user agent. There are a good number of gazelle+ocelot based trackers out there and the only ones who look at user agent as part of their whitelist would need to have done custom work to implement that. Link to comment Share on other sites More sharing options...
breakyrslf Posted April 16, 2014 Report Share Posted April 16, 2014 Is there any explanation for this ludicrous policy change? It is clearly screwing everyone's day up royally, especially torrent website staff, so why the hell has it been implemented? Link to comment Share on other sites More sharing options...
secretmethod70 Posted May 8, 2014 Report Share Posted May 8, 2014 Perhaps more importantly, is there any work being done to rectify this issue? It has now been over a month since it was brought up, and no word on whether or not it will be fixed. Should I be looking for a different client to use, or will this be fixed if I'm patient? Link to comment Share on other sites More sharing options...
Fangs404 Posted May 9, 2014 Report Share Posted May 9, 2014 What's the latest news on this issue? Link to comment Share on other sites More sharing options...
Zulithe Posted May 15, 2014 Report Share Posted May 15, 2014 Can developers please take this issue seriously? There are trackers out there that are blacklisting newer versions of uTorrent because the strings for stable versions are not unique from beta/rc/test versions. Please listen to your userbase. Tightly maintained trackers need to be able to properly differentiate between which clients are being used and in what state of development they are in. Link to comment Share on other sites More sharing options...
Medlir Posted May 16, 2014 Report Share Posted May 16, 2014 This has been a thorn in my side for weeks now as well. Constantly asked to update, and I want to and would, but can't because tracker sites can't reliably whitelist it. Link to comment Share on other sites More sharing options...
Fangs404 Posted May 31, 2014 Report Share Posted May 31, 2014 It appears this was fixed in 3.4.2. Changelog: -- 2014-05-29: Version 3.4.2 (build 31515) StableChange: Client now indicates non-stableness with a 'B' e.g. -UT341B- in Peer IDFix: Resolve antivirus compatibility issuesFix: Added information dialog after clicking on Help->Download TranslationFix: Regression in labels featureFix: Crash when removing trackers with confirmation dialog enabledFix: DHT regressionFix: Secondary sorting which is set by shift+click on a column headerFix: Incorrect text in the uTorrent Remote username/password notification dialogFix: Crash when downloading in Compact Allocation modeFix: Crash parsing malformed DHT messagesFix: Crash when writing resume file for torrent with no metadataFix: Crash when not removing torrents from the fairlistFix: Multiple other crashes Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.