HIding Areas {01}

On Sunday 22 June 2003 08:08, Ingo Brueckl wrote:

> Again, as I asked (without getting an answer) when Sean made this
> suggestion: Hide areas depending on what criteria? Doesn't filtering work?

Filtering works, but it is a bit limited in meeting this sort of request.  The 
problem here (and I suspect with Sean's system as well), is that the BBS is 
carrying the complete echomail backbone (well over 400 message areas), 
however there's only a few that I actually follow.  When reading with 
BlueMail, the whole (400+ area) list shows up, and I have to manually page 
through the list to find the few areas that I actually read.  In BBBS, each 
user is allowed to "subscribe" to selected message areas, and only those 
areas are scanned for new mail and such.

It would be great if BlueMail would either read and honor this "subscription" 
information from BBBS, or (preferred because it is more generic and can be 
universally applied) allow a separate list of the areas which should be 
displayed.  Any areas not on the subscription list would not appear in the 
list of areas (or be processed in any way via BlueMail).

> So far, we have the possibility of a long and short area list as well as
> the possibility set a filter on it.

And those work well, but are not really able to provide the filtering required 
for this particular request (unless I "bastardize" the message area titles on 
the BBS to provide some unique filtering criteria just for this purpose).

> What areas do you want to hide? Is it a BBBS specific demand?

Not really specific to BBBS.  More applicable to anyone operating a hub system 
with a lot of message areas.

>  BS> I do have one other question or potential "wish list" item...  Is
> there BS> a way to do "negative" filtering?
>
> I already thought about this, but while a "negative" filter isn't too
> difficult to realize, we'll soon talk about some boolean operators and
> regular expressions, which would be really hard work to implement.

I thought that might be the case.

>  BS> What I would like to be able to do is set up multiple exclusion
> filters
>
> Do you need them as a set of (say like 10) freely definable filters or
> fixed on a per area basis?

I can't imagine needing them on a per area basis (nor would I ask anyone to 
try to program that because I believe that would be a horrendous task).  
Personnaly, any (negative) filtering that I have in mind would be applied 
globally.

> I already though about adding a few input box macros (\0 ... \9). You'll
> define them in the rc-file and simply enter, for example, \4 in any input
> field (filter, search, letter header or whatever) to get it filled with
> what you defined in the rc-file for that. Would that be handy?

It probably would, although I usually forget about using the defined macros 
and retype all the stuff each time.  However, I don't think that really help 
the filtering requirements that affect folks like Sean and I.

>  BS> Really sort of a spam filter (or it has also been referred to as a
> twit BS> filter on some systems such as the original GoldED).
>
> A twit filter is on my todo list (but will require a lot of work).

I was afraid of that (the lot of work comment).  It's more of a "nice to have" 
than a "must have", for me.

Thanks.

Bob

--bluemail-----------------------------------------------------------
Post to the list by email to [email protected]
To unsubscribe email [email protected]
--POWERED BY MDAEMON!------------------------------------------------