This build turns off rejecting queries based on output bandwidth usage,
a feature that is unnecessary (we have other ways of limiting bandwidth
usage) and counterproductive to routing.
Maybe so, but I doubt having a "Data waiting to be transmitted" value above 30 minutes worth of transmission (with full bandwidth usage) is good for the routing, either.
I noticed the value notably lower in the latest builds (in the order of 5-10 minutes) with the bandwidth usage-based queryreject; I hope things won't get Mighty Bad again :)
Might a "I have the key you need but my band is full and can't send it right now, try searching with the other nodes meanwhile and come back later if you really need it" message help such situation?
-- /~\ The ASCII TLD \ / Ribbon Campaign "They that can give up essential liberty to obtain X Against HTML a little temporary safety deserve neither liberty / \ Email! nor safety." -- Benjamin Franklin
_______________________________________________ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
