Re: [leafnode-list] New or enhanced filtering in leafnode-2.0?

[Lloyd Zusman <ljz@xxxxxxxxxx>]

krasel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx (Cornelius Krasel) writes:

> Lloyd Zusman wrote:
> 
> [...]
> 
> There is a new filtering mechanism in the current alpha versions of
> leafnode-2.0. It can work with your examples:
> 
> > [ ... ]
> 
> newsgroup = news.software.readers
> pattern = ^Subject:.*[sS][lL][rR][nN]
> action = select

Ahhhh ... this is great!


> > [ ... ]
> 
> newsgroup = alt.binaries.*
> pattern = ^Subject:.*\.[jJ][pP][eE]
> action = select
> pattern = ^Subject:.*\.[gG][iI][fF]
> action = select
> 
> newsgroup = *
> pattern = ^Subject:.*\.[jJ][pP][eE]
> action = kill
> pattern = ^Subject:.*\.[gG][iI][fF]
> action = kill
> 
> (This works because patterns are worked on from top-to-down.)
>
> You can also score articles by doing "action = 5" or "action = -10".
> Doing "action = 999" is still different from "action = select", because
> only in the former case subsequent regexp's will be checked.

This also is great!

This is almost exactly the same logic that I used in my
proof-of-concept scoring filter from last year, but the syntax is much
clearer and easier to follow.  It looks like you based it loosely on
the slrnpull scoring filter, correct?


> The parser as used currently has still some drawbacks, especially that
> you cannot use # anywhere (most problematic for the regexp, I guess),
> because it is always interpreted as the start of a comment.

Maybe I can fix that ...


> > I'd like to fervently request that *some* sort of enhanced filtering
> > be put into leafnode-2.0, so that it can handle as a minimum the types
> > of cases that I outlined above in my examples.  Keep in mind that I
> > believe that this should be *optional*, [ ... ]
> 
> No, I think the original filter file format should be entirely
> abolished.  Otherwise, the parser gets much too complicated. It was
> only thrown together because I needed something quickly to filter
> the ARSBOMB spam. Change of version number is a good time to change
> formats as well, and we can include a conversion routine into "make
> update", if we want to.

Yes, I agree.


> [ ... ]
> 
> > Also, over the next week or so I'm going to write and submit another
> > proof-of-concept patch for a new filtering mechanism.
> 
> Before you are going to write something, I strongly recommend you should
> have a look at the new filtering mechanism. Maybe this may save you some
> work :-) Anybody who wants me to send a tarball of the latest alpha, just
> tell me. While it builds on 1.9.4, I have included all patches that were
> made in the 1.9.5-1.9.10 versions. However, it therefore features a
> rather impressive changelog :-)

Yes ... please send this to me!!!  ... or I'd be happy to download it
via FTP if that's easier ... I'm salivating as I write this!  :)

Thank you!!!


-- 
 Lloyd Zusman
 ljz@xxxxxxxxxx

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list