Re: [Mldonkey-users] Server black list

[Brett Dikeman]

At 8:10 PM -0500 12/13/02, Stephane Goulet wrote:

> Yes, that's right, that why i think it should be an option ;)

Except that your binary(on/off) suggestion(if I understood you 
correctly) would mean the user can't choose which networks to block. 
Perhaps they want to block all non-routeables except, say, 172.x.x.x. 
Basically what I'm getting at is that having a "block non-routeables" 
option all by itself would be too coarse a control(IMHO).

> Some company really uses donkey clients?

It was a hypothetical example :-)  My point was that whenever you add 
functionality, you should try to make that functionality as useful(or 
flexible) as possible...to a limit.  Too often highly flexible 
software becomes impossible to use.  Look at Cisco IOS for example. 
You can do almost anything with a Cisco router...except you might 
need to spend hours(or worse) learning HOW to do it :)

That said, I think giving the user the ability to add/modify/remove 
args from a CIDR list isn't asking much brain power of them, provided 
it is documented somewhere with a few examples.  Most of the time, 
they'd never really need to touch it anyway, except if they're trying 
to figure out why the heck their mldonkey client won't add a server 
on their private network.

There is a possible danger here to allowing the user to configure the 
blacklist, and that is that they might do silly things like block an 
HUGE range(or ranges.)  I can't off the top of my head think of what 
that would really get them, but beware the fools, for they are 
geniuses at being fools...

Brett
--