You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Who exactly would benefit from this? What can already not be done?
You get numeric 718 when UMODE +g is enabled and this can already be listened for (using @NumericFilter off the top of my head)
<- :tolkien.freenode.net 718 notZarthus bathtub_shark zarthus@trivialand/guesser/zarthus :is messaging you, and you have umode +g.
After that, the local client needs to consider whether to accept or reject (do nothing)
(09:54:36) accept ACCEPT <parameter>
(09:54:36) accept
(09:54:36) accept ACCEPT allows you to control who can send you a NOTICE or PRIVMSG
(09:54:36) accept while you have user mode +g enabled.
(09:54:36) accept
(09:54:36) accept Accepted users can also message you if you have user mode +R
(09:54:36) accept enabled, even if they are not logged in with services.
(09:54:36) accept
(09:54:36) accept For +g: /QUOTE ACCEPT <nick> -- Add a permitted nickname
(09:54:36) accept /QUOTE ACCEPT -<nick> -- Remove a permitted nickname
(09:54:36) accept /QUOTE ACCEPT * -- List the present permitted nicknames
(09:54:36) accept End of /HELP.
In short: I think we already support this through @NumericFilter, and you could make it an event and call .accept() or .reject() /* literally does nothing, may not even exists */ on it, but besides being nicer to work with for a VERY niche audience, I think no benefit is gained here.
Arguments could be made for support maintaining the ACCEPT list, but eh, I don't think it's an issue.
https://github.com/atheme/charybdis/blob/master/doc/modeg.txt
The text was updated successfully, but these errors were encountered: