Re: [Mldonkey-users] eMule bans in unstable-2-02-6

[MLdonkey]

>  > In two hours I banned half of the new emule comunity (1890 banned)...

Yes, the stats are broken. The clients are "seen" only when they ask
some file from you, so that you may ban clients that didn't ask you
anything (they are not added to the seen, only to the banned).

>  Perhaps it is the wrong way to BAN them completely in the first place.
>  But we have to check them at least every 30 Minutes or we'll get thrown
>  out of the queue (if we don't ban them). If your QR is >2000,
>  I doubt you'll get any data of this client *today*.
>  So banning is still better than collecting or dropping. If we drop them,
>  we receive them again and ask again (like a new client). For collecting
>  it needs memory and bandwidth (to check at least every 30 mins).
>  
>  MLdonkey: Is banning for the whole remaing client uptime? Or are the
>  entries removed after beeing banned for, e.g. 180 Minutes? This would make
>  sense then. Perhaps the eMule restarted/reconnected in the last 180
>  Minutes and we would get a new QR. Please think about it.

By default, clients are banned for 6 hours (the ban_period option). I
don't know what to think of that. It is an experimental idea. The
other point is that, if we ban them, we don't upload to them, and we
don't progress in their queue... Keep in mind that these CVS versions
are for experimentation, and should not be seen as official mldonkey
releases. We have to see what happens now (does the client suffer from
banning these emules ?). 

- MLDonkey