First, are you sure, that the above rules are matching the intended?
I.e. 'comp.os.os2...' or 'alt.binaries...'? To my opinion the
killgroup expression had to match the complete groupname (so would
that be a bug or a feature?).
Second, I don't want to contradict your rule of thumb. I thought
about such thing when I implemented scoring for VSoup, but found it
much too confusing. One globale killthreshold (you're right: the last
one in the file...) should be enough, also maintenance of the score
file would be too complicated with local killthresholds (my opnion
again).
BTW: does anybody uses group dependant killthresholds in Souper? My
idea of scoring is, that I can decide how much news I want to receive
today... If I have plenty of time, I'd set the threshold to let's say
-5 (and thus receiving a lot of b*llsh*t), if there is no time. I'd
set the threshold to '5'. And therefor (again) only one single global
killthreshold is required.
> Talk with you later,
We'll see...
Hardy
> If two million people do a foolish thing, it's still a foolish thing.
^^^
Why two million? Did MS only sell 2 million copies of W95, or what?
-- Hardy Griech, Ernetstr. 10/1, D-77933 Lahr http://privat.swol.de/ReinhardGriech/