Jilles Tjoelker

The consistent approach would be to generate an ECHO message back when the next server to send the PRIVMSG or NOTICE to does not support the ECHO capab. This would...

> There's also the problem of remote servers not knowing about what capabilities a client has enabled. The current code handles that by unconditionally sending back an ECHO message server-to-server...

This feels to me like an arbitrary change that damages the architectural integrity. For example, why does the same not apply to sending to channels unvoiced?

So the idea here is that some regexes will be drop and some will be superdrop? Otherwise, it would be simpler to remove the ability to set `+u` instead.

All this complexity seems only useful if there is a sufficiently large network that will use `filter_sees_user_info = off` and `filter_bypass_all = off`. Otherwise, we will just meaninglessly have this...