Slashdot Mirror

← Back to Stories (view on slashdot.org)

BitComet Banned From Private Trackers

Posted by ryuzaki0 on from the salt-for-my-leeches dept.

An anonymous reader writes "Slyck news is reporting that because BitComet does not recognize the 'private flag' on torrents originating from pirate BitTorrent trackers, this client is being banned from these communities. Private trackers are finding their torrents spread via the private DHT layer, allowing leechers to bypass ratios and download content freely."

3 of 447 comments (clear)

  1. Changing BitComet's User-Agent by Anonymous Coward · · Score: 5, Interesting

    Is there a way to change the 'user-agent' of bitcomet to make trackers think it's another client?

    1. Re:Changing BitComet's User-Agent by InvalidError · · Score: 4, Interesting

      The BC people could simply generate bogus agents or no agent at all.

      Trying to enforce artificial tracker-centric limits is pointless. Leeches and "freeloaders" can mod Azureus and other OSS BT clients to bypass/ignore artificial restrictions like 'private flag' and ratios. For ratios/leech-ban, anyone can mod an OSS client to make it report an arbitrary yet plausible upload count, a simple form of which could be U(n) = U(n-1) + k1 * (0.5+rnd()) * (D(n) - D(n-1) + k0). (where 0 = rnd() = 1 and k0/k1 are used to tweak the simulated traffic profile)... or even simpler than that, append an extra random digit to the upload volume and the ratio magically goes from 1:10 to 1:1.

      BT is one of the dumbest KISS protocols out there, keeping things locked up is one of the many things it was not designed/intended to do. Banning BC will only cause people to mod other BT clients to achieve their desired results and send BC-ban-happy sites back to the drawing boards.

  2. private/pirate by Chmarr · · Score: 4, Interesting

    The title says "private trackers", but the text says "Pirate trackers" once... Is this a typo, or fruedian?? :)