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...
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.
