-
Notifications
You must be signed in to change notification settings - Fork 180
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
auditorium mode #484
Comments
Hmm, some servers have Auditorium mode which is basically this: |
Although being a third party module of UnrealIRCd: https://gitgud.malvager.net/Wazakindjes/unrealircd_mods/src/master/man/auditorium.md |
I remember this mode being used on ircu(Undernet) on #Opschool, where noone could text, but users could ask questions via a bot, and with !next, the first user in queue was getting +m, so except for the @, only one user at a time was allowed to speak...like a ticketing system. Not sure about case usage except this. |
+v, sorry, not +m, the channel was +m. Sorry, I can't edit from phone. |
above comment^ so, except for the +m mode, on channel, since no user is able to speak, until and even after !next is invoked, the user could not see the fully populated userlist on the channel ( only @), like noone else was present on channel, just the @ and the !next given voice user. |
Thank you sir dan, ill wait for this enhancement soonest 👍 |
I have a draft of this lying around that I can revive... |
@scanned BTW, my guess about your config syntax issue is that you have tabs in the file (YAML requires the use of spaces, not tabs, for indentation). |
This is coming out of discussion in #ircv3 with the Ripcord developer. Conventional IRC channels are O(n^2) in the number of participants, because of the need to propagate all the JOINs and PARTs. One might think that this is unavoidable, because if n people are talking on a channel then the server has to propagate O(n^2) PRIVMSG's. But actually, channels are unusable if more than 100 or so people are talking at once, so the problem is mostly about JOIN, PART, and NAMES for channels where the number of listeners >> the number of speakers.
Idea: an "announcements" mode for channels that is like
+m
(only privileged users can speak), but which strategically suppresses JOIN, PART and NAMES once the number of users goes over a certain threshold. This would be a replacement for site-wide announcements channels on Slack or Discord.The text was updated successfully, but these errors were encountered: