On this basis, maybe the reasonable inference is we should use a tool that does not have this bug? ;)
I used RatioGhost, RM+, mR one after another on IPT and cheated ↑10T+ until now, no problem so far.
For your reference, the rules I follow:
- Reasonable speed (not too high, not too low, both too conspicuous. the same speed as most people show on peerlist is better)
- When downloading, upload speed should be set much lower than download speed. Don't let torrent ratio reach more than 1 the moment it just finished. too fake.
- Memory reader.
- Choose swarm torrents (avoid pack bc there are partial leechers)
- When leecher of a swarm torrent becomes small later, stop cheating on it.
- When seeder becomes 0 for downloading torrents, stop cheating on it or pay close attention to the progress bar on peerlist to prevent your progress from running ahead of everyone else (even becoming the only one who has finished it) and causing exposed.
- Disperse cheating traffic and time. Creating little fake uploads on 50 torrents is obviously less noticeable and detectable than creating huge upload on only 1 torrent. Similarly, cheating 50G/day for 20 days is less noticeable than cheating 1T in only one day.
- Never appear on the top10 list, whether it is Top10 Upload, Top10 Upload Speed, Top10 Total Seeding, Top10 Seeding Size or whatever. Never comment. Speak in the forum as little as possible. Keep low key.
- Better not cross-seed. If have to, avoid those exclusive ones, choose those can be obtained from other trackers.
- Using randomization, do not let all torrent speeds be the same at all times.
- If cheating with uTorrent old version 2.X, do not choose torrents over 1T, which will definitely cause exposed, bc uT 2.X does not support torrent over 1T.
- Don't cheat always. some normal torrents/time, some cheating torrents/time. the more mix them up, the harder for staff to target us.
This set of principles apply to most trackers. Whether also applicable in cabal trackers? idk bc never dare to experiment, hope got to know someday...
---------- Post Merged at 10:08 ---------- Previous Post was at 09:32 ----------
Personally, I dont like use Waffles Method and "Dont send complete flag" feature. This is also what I want to exchange views with experts here, because idk if this analysis is wrong.
Although there seems no reports so far that some using Waffles Method are got caught, but in theory, these 2 features have highly obvious footprints to trace. Waffles Method send too many STOP announces compared to not cheating. As long as the tracker start recording the number of times we send STOP, we will be exposed. For "Dont send complete flag" feature, like the screenshot
<here> shows, tracker already record the number of our Downloads and Snatched, they just need to do a division X = Snatched / Downloads. If someone's X is too low, he has a high probability of being those who overuse the feature "Dont send", then staff can begin to examine him in more detail.
The question is whether tracker willing to cost lots of resources to let a programmer code these things. someday they're willing, then we become highly risky using these 2 features. So personally not use them anymore....