Enhanced Twitlist options
Re: New feature?
By: Angus McLeod to Deuce on Fri Nov 11 2005 12:00 am
> > Would probobly do the trick... opinions?
>
> I'd be interested in seeing more diverse control over which messages get
> twitted. The trigger is currently the name of the user in either To: or
> From: fields of the header. You have asked for twitting by sub-board.
> What about twitting by subject? By size of message? By ratio of quoted
> lines to response lines? By date? By origin? What about allowing 'real'
> RE's (pcre) instead of only simple strings? Allowing the RE to match
> against the body? What about passing the message (header and text) to an
> external program and twitting the message based upon the return value of
> the program? And of course, any logical combinations of these?
>
> There is an absolute BOAT-load of expansion that could be added to the
> filtering mechanism. Perhaps too much for us to expect any time soon?
> But if the twitlist format is going to be altered, I'd like to see it
> altered in a way that will allow these other features to be incorporated
> at a later date.
>
> Also, I'd like to see per-user filtering at message delivery, rather than
> per BBS filtering upon message receipt. That would allow a SysOp to
> receive and accept messages, and have the users select individually who
> they will twit, and who they won't, when creating individual QWK packets
> or reading online. This would also allow for twitting messages from every
> source, since the filtering is done at time of reading, not at time of
> packet receipt.
Re: Paragraph 1
Possible, but since I don't have a personal use/need for it, it's unlikely that
I'd do it. One that are simple (size/date/origin/subject) yes. Passing to
external, no. Real RE's, yes but only of PCREs were already included for some
other reason. If you create a feature request at http://bugs.synchro.net/
it'll be remembered.
Re: Paragraph 2
The simple stuff could be done at twitlist overhaul time. When you see a
twitlist .ini commit, speak up and remind us while it's fresh in one of our
minds.
Re: Paragraph 3
Definately a good idea. Probobly should be done at time of message reading
overhaul. Again, remind when you see an associated commit.
---
■ Synchronet ■ My Brand-New BBS (All the cool SysOps run STOCK!)