<Monkey> I believe it could be useful to ignore certain messages based on variables that a user is able to define. It might just be a client issue but perhaps some filtering should happen in psyced?

Method Filtering

There is an entry in the CHANGESTODO about this, it suggests to extend the /ignore syntax to

/ignore <source> <method>

with <source> matchable by * ?

In a way this even looks similar to the semantics of /ignore in ircII (thus presumably also mIRC).

Method filtering however isn't always the right answer to every problem, because what you actually might want to have is Channels so you can unsubscribe the Web Inspection notices from a chatroom without leaving it and without receiving them in the first place.

Since Channels are a tougher thing to implement, we could start out with method filtering. Sure.

Theoretically one could make a super complex filter specification language, something like

_source == psyc://psyced.org/@psyc && (mc == _notice || _action == giggles)

but uh, over the top and not within priority range. I'd rather run PSYC thru procmail instead, haha ;)

Channels

<Monkey> It sounds like Channel is the answer to what I had in mind. Specifically: filtering those Web Inspection things. Maybe something like the way debug logging levels are implemented in so many unix programs. I could set my notice level to 5 but all those inspection notices are a level 1 so I don't see them (Slashdot scores come to mind as well but scores wouldn't really be variable). Could be easier to compare an int instead of very complex expressions. I don't think it needs to be complex at all. Also, could this be a way to implement simple channels? Keep a sorted list of everyone, then the notices could be distributed efficiently stopping at the point in the list where the level' numbers exceed the level of the notice.