Using KTorrent 2.1beta1 on KDE 3.5.5.

Last night I was banned from a private tracker called OiNK (http://oink.me.uk). I was also banned from their IRC server, so it took me quite awhile before I was able to figure out the reason for being banned.

After using a friend as my mouthpiece to communicate with one of their mods over IRC, they told him I was banned for 'cheating.' Dumbfounded, I asked them to define what 'cheating' meant (since I've never heard of such a thing and my ratio was well above their minimum requirement). Without explaining what he meant by 'cheating' their mod decided not to help at all. He insisted I was cheating and that I was no longer welcome. He refused to look into any aspect of the matter. The guy's name was 'Teoulas.'

Anyways, after noticing there were past threads on these forums reporting issues with OiNK's 'cheat detection', I've decided to explain my situation here. Perhaps you should contact the OiNK admins again and ensure there aren't any outstanding bugs regarding this matter.

If there are any OiNK administrators reading (since I noticed they've posted here in the past for this very issue), I request my ban to be appealed. I contributed some great rare gems to your community as a new user, and as a reward I am mistakenly banned as a cheater. Quite unsettling, especially since the friend who invited me (who also donated to your servers btw) may be penalized for my false ban.

Cheers.

It seems like KTorrent and OiNK don't get along too well?

It has to be due to the eye- and mindhurting colours of their homepage

I believe all the tracker bugs where fixed in 2.1beta1, currently there are no unfixed bugs in this area.

It would be interesting to know what kind of cheat detection they are using, but they will probably not tell us that.

We have contacted them before, they banned KT because of some bugs, we resolved those and then they unbanned us again.

So lets see what we can find out. But we should be diplomatic, don't want to get KT banned again for **** of the admins.

Aye, both sides have good intentions here.... Perhaps it's better if George/Ivan communicated with OiNK rather than any of us, since they would know best what to say

I will try, but I wouldn't expect much...

Private tracker admins/mods are not very pleasant when there's cheating involved. The last time I had to explain a situation with KTorrent I spent about 10minutes trying to explain the problem without being misunderstood. Eventually, someone in the better mood comes in and listens to my problem.

Anyway, I'll try getting in touch with OiNK admin that proved to be quite open for helping the last time and hopefully we can sort this out. I cannot guarantee that we will, though.

@caustiq: You're absolutely sure you weren't cheating? They consider ANY modification of the client in ANY way as cheating. So, even the slightest code change could be interpreted as cheating. Also, try to remember did you have any 'unusual' operation recently. Something like a large torrent import, network connection problems or something similar that could cause KTorrent to misbehave. Log files would probably be very helpful but I doubt you saved them.[/quote]

I've made no code changes at all. Compiled straight from portage on gentoo.

The only usage that I might consider abnormal is when I was seeding about 7-10 torrents all at once. Usually I seed only 3 at a time, and any others get queued, but I was making an effort to give my ratio some breathing room. Most of the seeded torrents had 0 leechers anyways.

I really don't care about getting my account back as much as I would like to ensure the problem is on OiNK's end and not KTorrent's. Good luck with the OiNK admins Ivan, from my friend's dealings with them, they aren't too receptive to criticism or interested in helping their users.

Edit: Ivan check your PM inbox for a link to the log file.

Say, this log file is the latest log before you've got banned? If so, I'm just curios how/why did you save it, since the next KTorrent start (where you got that ban message, right?) would overwrite the old log?

Anyway, there's some weirdness in it and I need to discuss it with George first.

Actually I haven't restarted KTorrent since I was banned. They give you a message in the tracker status if you are banned.

I've just received info from OiNK admin and I must say they did have a reason to believe you were cheating.

I'm not sure there's much we can do about it unless we can prove it was KTorrents fault. Even if that's true, I don't know if they will consider unbanning you.

We'll need to check this behavior and I'll let you know how it went.

interesting. I am having problems with wildly ridiculous stats on Demonoid. in one night, both my uploads and downloads jumped by 100 GB, and my share ratio dropped from about .65 to .45.

there's no way on earth that i have enough upload b/w to upload 100 GB overnight. i don't know if its the tracker or if its ktorrent, but my stats are not reliable.

fwiw, that happened before i upfgreaded to 2.1-rc1.

Problems with Ktorrent and Oink ? I have to say i'm always using latest svn of Ktorrent since a few months and never had trouble with oink (except the little bug a couple months ago that was fixed quickly) and i'm always seeding 30+ torrents. But I have to say I didn't use oink the last couple of weeks, so I hope everything is still fine.
I just really hope you didn't cheat and that's an error from a Oink admin, but I think they are really some of the best tracker admins I know (considering Ktorrent is banned from bitsoup...).

bob p wrote:interesting. I am having problems with wildly ridiculous stats on Demonoid. in one night, both my uploads and downloads jumped by 100 GB, and my share ratio dropped from about .65 to .45.

there's no way on earth that i have enough upload b/w to upload 100 GB overnight. i don't know if its the tracker or if its ktorrent, but my stats are not reliable.

fwiw, that happened before i upfgreaded to 2.1-rc1.

I vaguely recall coming across a bug report with identical symptoms... here at the forums if I'm not mistaken. It was definitely pre-2.1, and I don't recall the final resolution.

I know (considering Ktorrent is banned from bitsoup...).

allowed now, but tracker give an error , whitelist does have an upload .....

Allright, after checking out the log files and doing some experiments we have come to the following conclusion :

There was a pretty obscure bug in 2.1beta1, which under certain rare circumstances could lead to a wrong downloaded number to be reported to the tracker.

Oink interpreted the wrong downloaded number as cheating.
Seeing that we promissed oink not to disclose any information about their cheat detection, I can't really elaborate on the details.

We also did the same tests with 2.1rc1 and the latest SVN code, and this bug does not show with those versions. So the bug was fixed in 2.1rc1. The chance that you get this is not that big, but it is possible.

We will contact oink, to explain the problem, and ask them to unban you.

Anybody who is still using the beta on private trackers, should upgrade to 2.1rc1.