-
Notifications
You must be signed in to change notification settings - Fork 181
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
registered channels should always be active #1507
Comments
Hello People & Happy New Year! Hope this message finds all of you safe, healthy and happy! |
Ah, it's not necessary to reproduce the |
I am not sure a separate registered mode is required, but I agree on ChanServ or similar joining if there is only one non-op present to avoid some (misconfigured?) clients attempting to autocycle for gaining ops. I think Atheme ChanServ does that too leaving once there are two users in the room. I think empty rooms could simply stay empty until the first user appears. |
This isn't necessary in our implementation either --- if a channel is registered, even if you are the first person to join it you will not get +o. (This is an aspect of "services" being fully integrated into the ircd: the ircd always knows whether a channel is registered.) |
The point of the behaviour I described is to stop the client from infinite cycle looping as it won't understand channel being registered |
Ah, that makes sense. I still don't really want to have ChanServ joining channels (that feels like "legacy IRC" to me). |
:) its not that bad. :) |
Registered channels should be eagerly created on startup, and should remain (and be visible in LIST) even when they have no members.
See #1477 and #704 among others. This is a proposal to simplify some logic:
LIST
outputThe text was updated successfully, but these errors were encountered: