g0> Twit filters in their current state are for filtering a specific user's
 g0> messages.
 g0> 
 g0> I haven't had any plans to support wildcards as I don't personally see
 g0> the benefit.  If I were to Twit "Jeff*" it would unfairly hide a lot of
 g0> messages from current and future Jeffs that may not be the person I
 g0> wanted to twit.
 g0> 
 g0> Another thing I would want to take into consideration for supporting
 g0> wildcards here is that the twit filters in general slow down message
 g0> searches, so the more complex I make that function the slower searching
 g0> through messages will become.

Yes I understand that, it would become cumbersome. However, it would be a
great benefit to have wildcards for instances like this (which I might add
this twit has many variants) The SHPAMMER ish jew paedophile BAR where the
common part of the field is SPHAMMER I could enter *SPAMMER* and catch them
all. 
This example is real and took me a couple of tries to get all variations in
the TWIT list. If this twit comes back with a new variant, it will have to be
added as a new twit filter.

If you did implement wildcards it would have to be stressed
greatly that the results may not be what the sysop intended if they chose to
use the wildcards. I would think we as sysops could manage it.
Just my 2 cents.

Thanks for the reply.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/64)