Author Topic: Utorrent spoofing removed?  (Read 12399 times)

nevernow

  • Member
  • **
  • Posts: 28
  • Karma: +0/-0
    • View Profile
Re: Utorrent spoofing removed?
« Reply #15 on: September 20, 2010, 06:51:20 pm »
Sequential downloading IS harmful. It clashes against the smart algorithms the bittorrent protocol is based on and worsens the health of swarms (sometimes fatally). While I wouldn't want it to disappear as an option, it should not be abused.
« Last Edit: January 01, 1970, 01:00:00 am by Guest »

fbar

  • Guest
Re: Utorrent spoofing removed?
« Reply #16 on: September 21, 2010, 04:51:33 am »
That's the point exactly. All it takes is an admin who thinks just a little bit stronger about it.
« Last Edit: January 01, 1970, 01:00:00 am by Guest »

nevernow

  • Member
  • **
  • Posts: 28
  • Karma: +0/-0
    • View Profile
Re: Utorrent spoofing removed?
« Reply #17 on: September 21, 2010, 06:59:51 pm »
I certainly dislike admins enjoying powertrips and using a pointless "guilty until proven innocent" approach towards clients, while not taking time to actually test them.
And I certainly find it legit to circumvent stupid rules (in life, not only in torrents).
« Last Edit: January 01, 1970, 01:00:00 am by Guest »

christophe.dumez

  • Administrator
  • Veteran
  • *****
  • Posts: 179
  • Karma: +10/-0
    • View Profile
Re: Utorrent spoofing removed?
« Reply #18 on: September 25, 2010, 08:40:37 pm »
This was not an easy decision. I eventually decided to remove this workaround because it has an negative impact on qBittorrent reputation. Removing this feature already helped getting whitelisted on 2 private trackers (that I know about) and it will hopefully continue.

Regarding the sequential download feature, I'm aware of the official position on this matter. Note that qBittorrent never applies *strict* sequential download.
qBittorrent merely advises the piece picker to choose the first pieces first but the piece availability is still taken into consideration and the Bittorrent algorithm is still in place although altered. Just to say that it is not as bad as it seems. I did not receive complaints about this yet (hopefully I won't).
« Last Edit: January 01, 1970, 01:00:00 am by Guest »
qBittorrent author

fbar

  • Guest
Re: Utorrent spoofing removed?
« Reply #19 on: September 27, 2010, 07:39:29 am »
Quote from: "christophe.dumez"
Just to say that it is not as bad as it seems.
It's not. On most private trackers the seed/leech ratio is so ridiculously high that the actual algorithms don't have any impact on the network whatsoever. The problem is in the heads of people. And it's not solvable -- the only way is work around it.
« Last Edit: January 01, 1970, 01:00:00 am by Guest »

fbar

  • Guest
Re: Utorrent spoofing removed?
« Reply #20 on: October 10, 2010, 12:23:16 am »
Ok, here's a simple patch to simulate uTorrent on qBitTorrent 2.4.4. Only use it if you need that bad. There's no option to choose versions etc - everything is hardcoded. This is dedicated to people like me who either has to use the older version, or not to be able to download stuff from some trackers otherwise.

Code: [Select]
diff --git a/bittorrent.cpp b/bittorrent.cpp
index 1c51d1c..5c88038 100644
--- a/bittorrent.cpp
+++ b/bittorrent.cpp
@@ -93,11 +93,11 @@ Bittorrent::Bittorrent()
   // Creating Bittorrent session
   // Check if we should spoof utorrent
   QList<int> version;
-  version << VERSION_MAJOR;
-  version << VERSION_MINOR;
-  version << VERSION_BUGFIX;
-  version << VERSION_TYPE;
-  const QString peer_id = "qB";
+  version << 1;
+  version << 8;
+  version << 5;
+  version << 0;
+  const QString peer_id = "UT";
   // Construct session
   s = new session(fingerprint(peer_id.toLocal8Bit().constData(), version.at(0), version.at(1), version.at(2), version.at(3)), 0);
   std::cout << "Peer ID: " << fingerprint(peer_id.toLocal8Bit().constData(), version.at(0), version.at(1), version.at(2), version.at(3)).to_string() << std::endl;
@@ -396,7 +396,7 @@ void Bittorrent::configureSession() {
   }
   // * Session settings
   session_settings sessionSettings;
-  sessionSettings.user_agent = "qBittorrent "VERSION;
+  sessionSettings.user_agent =  "uTorrent/1850(17414)";
   std::cout << "HTTP user agent is " << sessionSettings.user_agent << std::endl;
   addConsoleMessage(tr("HTTP user agent is %1").arg(misc::toQString(sessionSettings.user_agent)));
« Last Edit: January 01, 1970, 01:00:00 am by Guest »

nevernow

  • Member
  • **
  • Posts: 28
  • Karma: +0/-0
    • View Profile
Re: Utorrent spoofing removed?
« Reply #21 on: October 24, 2010, 10:49:52 pm »
In version 2.5.0 beta1, you need to patch qbtsession.cpp in src/qtlibtorrent/ (again, hardcoded to uTorrent 1.8.5). Can't we just have the spoofing feature back?  :evil:
I will take a look at 2.5.0 beta2, things seem to have changed again.

You can find the edited qbtsession.cpp file here: http://pastebin.ca/1972159
« Last Edit: January 01, 1970, 01:00:00 am by Guest »

FlacMonkey

  • Guest
Re: Utorrent spoofing removed?
« Reply #22 on: October 25, 2010, 05:45:40 pm »
Any spoofing feature once discovered being used by a member results in a ban without warning from any private tracker. Having an official release with an built-in spoofing feature is a reason enough for any private tracker not to allow such client. It is indeed a good thing for qBit not to have this feature anymore. Removing client spoofing resulted in qbit being allowed on several major private torrent sites. It's the only way to go to gain private trackers' trust and gain popularity. Often, starting a thread in private sites' forums or contacting staff will be enough to get them to add qbit to the clients whitelist. Qbit is a very neat little client that's perfectly reliable and works well and fast. Now there's no reason for it not to be allowed on private sites.
« Last Edit: January 01, 1970, 01:00:00 am by Guest »

nevernow

  • Member
  • **
  • Posts: 28
  • Karma: +0/-0
    • View Profile
Re: Utorrent spoofing removed?
« Reply #23 on: October 26, 2010, 12:30:35 am »
This has already been discussed, but...

You see, we all know qB is a fair and good client, based on a well known third-party bittorrent library. There is no reason to blacklist it on any private tracker. The problem is most trackers have whitelists, not blacklists, and they're mostly unmaintained.

A client which allows spoofing may not be allowed on a tracker, but at least it will be used there. Removing the function locks out that client from the tracker until when (it could be never) lazy and/or power-tripping admins decide to allow it.

In a perfect world this wouldn't be an issue, but currently it is. All in all, a bittorrent client is a means to an end. The day I can't hack spoofing back into qB  anymore and I'm forced to choose between abandoning qB or abandoning the private trackers I use, I will have no doubt.
« Last Edit: January 01, 1970, 01:00:00 am by Guest »