BakaBT > Torrent/Tracker Issues
Found a ratio hacker/cheater? Report it here
AnimeOokami:
http://bakabt.me/user/210238/page.html
Uploaded 2991.27 GB (ratio 7849.6x ) on this torrent http://bakabt.me/149555-the-seatbelts-yoko-kanno-mai-yamane-souvenir-of-tokyo-live-cowboy-bebop-soundtrack.html
but it has been completed only 677 times.
AnimeOokami:
http://bakabt.me/user/956031/crissio.html
He has uploaded 4492.22 GB (ratio 7857.1x) on following torrent (on his seeded tab)
http://bakabt.me/151736-bloody-monday.html
but it has been completed only 789 times.
eristic:
This user:
http://bakabt.me/user/710700/shadowy.html
has sane statistics. But on two torrents I've uploaded I came across the following discrepancies:
http://bakabt.me/150009-windy-tales-ost-op-single-mp3-320-kbps.html
http://bakabt.me/150161-kenran-butou-sai-ost-singles-vg-ost.html
S/he has been seeding for significantly longer than the uploader (that's me) and has more hits, too, for much smaller upload volumes.
Checking her/his user page it looks very clean, except for:
1. seeding a huge number of torrents (could be possible given s/he is/says is from Norway),
2. very erratic pattern of ratios on individual torrents,
3. a very neat total ratio of ~1.002 (fluctuating only in the third place after decimal point over time) indicating either a cheating client or one that keeps track of transfer totals very accurately and over a long period,
4. an unusual number of 0 KB downloads on non-freeleech torrents (mostly soundtracks).
Specifically regarding (4), it's impossible for the two torrents I have uploaded since I personally encoded and/or tagged the albums. In one of them a BakaBT user specifically provided one of the albums for the torrent. In other words, it is simply impossible for the user shadowy to have had the exact same files and to have seeded them without leeching any.
Or maybe I have missed something and s/he is an honest user.
Blanchimont:
--- Quote from: eristic on June 22, 2010, 02:50:55 PM ---Checking her/his user page it looks very clean, except for:
1. seeding a huge number of torrents (could be possible given s/he is/says is from Norway),
2. very erratic pattern of ratios on individual torrents,
3. a very neat total ratio of ~1.002 (fluctuating only in the third place after decimal point over time) indicating either a cheating client or one that keeps track of transfer totals very accurately and over a long period,
4. an unusual number of 0 KB downloads on non-freeleech torrents (mostly soundtracks).
Specifically regarding (4), it's impossible for the two torrents I have uploaded since I personally encoded and/or tagged the albums. In one of them a BakaBT user specifically provided one of the albums for the torrent. In other words, it is simply impossible for the user shadowy to have had the exact same files and to have seeded them without leeching any.
Or maybe I have missed something and s/he is an honest user.
--- End quote ---
1. Seeding a lot of torrents isn't an issue, though too many might give issues for your pc and give very small piece of the bandwidth cake to individual torrents, and cause some overhead...
2. So? Some torrents don't almost ever have leechers, it's compensated by seeding those that do...
3. The bigger the amount downloaded/uploaded, the easier it is to stay at a level. For example I have 1.017 with 842.86GB/829.13GB up/down. Don't want it to slide down below one, and doubt he wants it either. Depends a lot on the type of connection one has.
4. He might have just used the public key, or got it from another source, to protect/raise his ratio. In your example he most likely used the public key.
I wouldn't be too quick to judge here, perhaps just keep an eye out...
eristic:
--- Quote from: Blanchimont on June 22, 2010, 03:36:01 PM ---1. Seeding a lot of torrents isn't an issue, though too many might give issues for your pc and give very small piece of the bandwidth cake to individual torrents, and cause some overhead...
2. So? Some torrents don't almost ever have leechers, it's compensated by seeding those that do...
3. The bigger the amount downloaded/uploaded, the easier it is to stay at a level. For example I have 1.017 with 842.86GB/829.13GB up/down. Don't want it to slide down below one, and doubt he wants it either. Depends a lot on the type of connection one has.
4. He might have just used the public key, or got it from another source, to protect/raise his ratio. In your example he most likely used the public key.
I wouldn't be too quick to judge here, perhaps just keep an eye out...
--- End quote ---
First off, do you have any comments on the two discrepancies I noted?
Then...
On (1) you're correct, except that seeding 117 torrents at once can create bursts of traffic on announces. A good connection is required for that but I suppose in Norway such connections are pretty much commonplace.
On (2), no, that's not the point. What's the point of downloading a torrent file for a few GB of files, feeding it to the client, downloading nothing (apparently, you need the files present to not need to download anything), seeding a couple megabytes, and then stopping there. It's erratic, to say the least.
On (3), again you're correct but people usually keep a desired ratio by attempting to seed every individual torrent they leech to that ratio. If you have many different ratios, cf. (2), on different torrents you'll need to either have a client that keeps transfer totals (and over long periods) or you'll need to constantly keep an eye on your ratio via some interface/API BakaBT provides.
On (4), if you use the "public key" (which, AFAIK, is not a session key at all, rather a different tracker) the session can't be identified as yours, can it?
On avoiding quick judgment I'm all the way with you.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version