Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider usermode +g / CALLERID support #32

Open
mbax opened this issue Aug 29, 2015 · 2 comments
Open

Consider usermode +g / CALLERID support #32

mbax opened this issue Aug 29, 2015 · 2 comments

Comments

@mbax
Copy link
Member

mbax commented Aug 29, 2015

https://github.com/atheme/charybdis/blob/master/doc/modeg.txt

@mbax mbax modified the milestone: After 1.0.0 Nov 1, 2015
@kashike
Copy link
Member

kashike commented Mar 29, 2016

Can now be found at https://github.com/charybdis-ircd/charybdis/blob/master/doc/features/modeg.txt

@Zarthus
Copy link
Member

Zarthus commented Mar 10, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants