Bonushogger?
Interestingly enough, this user has been mentioned elsewhere. I would suggest resetting any peer bans in your client and then get connected to this seed and see if the pieces received are corrupt. Actually I might just check this myself, only out of curiosity
not because I think they are guilty.
update: A major concern I have right now is that the peer in question is being reported by the tracker as a 'seed' but in fact appears to be a leecher (
on two different torrents). Not a hard thing to do, that is, trick the tracker into thinking you're a seed with 100%. I'll keep an eye on things for the time being, and re-stress that I'm not implying guilt. The user does seem to be connecting from a great distance on DSL so connectivity issues are quite possible. Although, the host address for this peer is looking suspicious too.
update2: From what I can see, this is kickban material
- On each of three different torrents, the peer is reported by the tracker as a 'seed' but in fact does not even have 100%
- On each of the three torrents, people had the same discussion about the user ignoring PM's (trivial, yes I'm aware, but..)
- The tracker statistics for the peer were available up to 13 days ago, when a member made some comments about his incomplete status and a possible glitch with the tracker information. Now the statistics are hidden without even commenting back (in the noted situation), or solving the problem. It took a different member contributing to the swarm to solve the problem.
- I've been choked the entire time connected to this peer, and the peer has been inactive the entire time. Even at ridiculously slow speeds, there's no reason to be choked the entire time.
- Do I even need to comment about the BitComet version in use?
- The host address is questionable at best.
I'm not the type to go on a ruthless witch hunt, so I'll leave it to the staff to investigate this further.
