Is there any reason to send data to bad(community mods or any other kind of leechers) clients ? What will they do with the data they leeched from us ?
What if they only want to download and consume that particular file? I can't see anything wrong with that as long as you don't want to have anything from them anyway. When
you are on the uploader side, why do you care about those downloading?
Isn't it better to upload data to clean clients ? They will probably share them with all the clients.
They can as well unshare the files. But how should the CA find out properly if a client is a leecher if you don't give it a chance to give you something back?
Why do you recognize common GPL breakers as "bad" ?
Because no-one can tell what they actually do.
And what do you mean by "common" ?
Those which are quite often seen.

Most of the leecher clients are GPL breakers. And any reason to detect them if you don't ban(usual ban or reducing score) them for leeching ?
Of course they are score-reduced when they leech. This is how CA works.
I don't know your mods. But i see there is lots of CA mods with AJ detection. Why do they doin' this ?
Upcoming beba and AnalyZZUL versions will check the mod string for "Applejuice" and its descendants, but this is (as you might know) no actually secure way to identify them. They do this for two reasons: First, they are GPL breakers (see above); second, they can't be configured to stop leeching. In fact, most "leecher" mods (like ZZULtimativ etc.) can be configured to work properly, so that's why a mod string detection basically fails.
From WiZaRd's original code comments:
- Code: Alles auswählen
these clients CAN IMPOSSIBLY be used as "good" mods - thus they do not deserve a single byte - very sad...
I said that I always wanted to try a mod with CA+dLp. I am looking forward to this.
The DLP system is made for punishing "suspect" mods. And it
does, even if they are actually releasers. Not always a good idea (you might lose a lot of sources), is it?