Im sick to death of watching bitcomet clients not sharing unless you have a bitcomet client. So I have an easy fix, can you add a feature were users can block all uploads to a set client type. anything other than the same client.

Its really annoying sitting there for hours with 30-100k uploads to bitcomet clients but Im getting nothing back.

So fair is fair, univeral bitcomet snubbing, let them suck on air till they learn it doesnt pay to not share.

Well, i'am not a developer but i like to share my thoughts on this.

Client blocking wil only make them share mods to spoof there piece of ****. I agree that sharing with bitcomet clients is not worth it most of the time, but banning on client type would not be a solution. Also, KTorrent might get a name the developers not want.

A good algorithm with a nicer value the developer already suggested to me on this forum would be a better solution i think. But i agree, bitcomet is a BIG pain in the **** since the main part op the bitcomet people are hit and runners or don' t share pieces, it' s very sad.

Punishing snubbers is a better solution, then just blocking. Because that will only force those clients to spoof their identity.

Ok thats sounds better, an anti snubing algorithm that will turn the tables so they get nothing.

Your either sharing or bugger off.

Or even <evil thought> when ktorrent see's a bitcomet client kt lies and says "yep Im a sad bitcomet client also, so share with me"

Or even <evil thought> when ktorrent see's a bitcomet client kt lies and says "yep Im a sad bitcomet client also, so share with me"

That is a possibility

I think the best solution would be making an algoritm that doesn`t upload to those that don`t upload nothing ,fake versioning is not a solution.Put an option in ktorrent : don`t upload to users who have a shair ratio lower than X(this could be customized by the user) or another option : upload to users as fast as they upload ,these are my suggestions ,these options should be available in general ,or torrent specific.This would tell the bitcomets "hey if you don`t give nothing you get nothing" or "you get as much as you give" ,and noone could say that we are discrimanating clients.

DjDarkman wrote:I think the best solution would be making an algoritm that doesn`t upload to those that don`t upload nothing ,fake versioning is not a solution.Put an option in ktorrent : don`t upload to users who have a shair ratio lower than X(this could be customized by the user) or another option : upload to users as fast as they upload ,these are my suggestions ,these options should be available in general ,or torrent specific.This would tell the bitcomets "hey if you don`t give nothing you get nothing" or "you get as much as you give" ,and noone could say that we are discrimanating clients.

It is impossible to know the share ratio of other peers.

Maybe something like this:
sr = bytes he uploaded to us / bytes he downloaded from us

though I don't think we keep track of this info...

I`ve heard that bittornado can...i read it in their forums.

The leoxv choker(very effective for anti-leech btw) in the rufus client checks the ratio from a peer on your own client and not the total ratio from a peer, maybe(and i expect) that's how bittornado also does this.(?)

Probably, it is possible to know how much a peer has downloaded from other peers, because of the HAVE messages. But upload is impossible, you can only know how much a peer has uploaded towards you, not towards other peers.

I was planning a niceness system, so a good inter-peer share ratio, will certainly contribute towards a better niceness value. But it cannot be the only criteria, new peers who have nearly nothing should be cut some slack (so they can get started).

To supply this topic with the information, this is how the choker i talked about let itself configure:


Pretty advanced configuration if you ask me, propably even a bit too much for people who don't know what they're doing. (they can mess it up bigtime).

What it doesn't take into account is to exclude people with like 0% of the data. And the way it works has a negativity:
it only get working on the job after you have uploaded the configured amount of upload to a certain peer, which takes away the option to say: "hey, you're a bad client? Alrighdy, suite yourself, but i like peers who do follow the protocol more than you so you're last in row.

Personally i don't think a whole different choker is needed, just build it into the standard one with the great nicer value idea.

I think you're a bit to spammy QBoy, and seriously, we are not the kind of button horny windows using people you're looking for.

Do yourself a favour and leave.