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

Support server-wide mute #2105

Open
luxaritas opened this issue Dec 13, 2023 · 3 comments
Open

Support server-wide mute #2105

luxaritas opened this issue Dec 13, 2023 · 3 comments

Comments

@luxaritas
Copy link

Currently, ergo supports the m extban when setting modes in order to prevent a user from sending messages to a particular channel. It would be great if this could also be done server-wide (ie, with UBAN).

Use case: A classroom of misbehaving students joins our website with an embedded multi-channel chat. Our moderators should be able to prevent any users from their IP from speaking (so that students who aren't at fault can at least still read chat, even though we need to take more decisive action to prevent active abuse) without having to do so for each individual channel.

@poVoq
Copy link

poVoq commented Feb 24, 2024

I agree this would be useful and maybe a /defcon setting to make all channels moderated would be good as well.

Currently defcon does:

DEFCON [level]

The DEFCON system can disable server features at runtime, to mitigate
spam or other hostile activity. It has five levels, which are cumulative
(i.e., level 3 includes all restrictions from level 4 and so on):

5: Normal operation
4: No new account or channel registrations; if Tor is enabled, no new
   unauthenticated connections from Tor
3: All users are +R; no changes to vhosts
2: No new unauthenticated connections; all channels are +R
1: No new connections except from localhost or other trusted IPs

I would propose to add +M for all channels to defcon level 3

+M would have the advantage over +R for channels (as defcon level 2 does) that non-registered users can still join and read channels and figure out what is going on.

@slingamn
Copy link
Member

I think this might be too extreme for level 3.

As I've learned from painful experience, without +R, spammers can exploit NICK and PART to spam channels...

@poVoq
Copy link

poVoq commented Feb 25, 2024

2.5 then?

I think there is a need to balance between anti-abuse measures and still allowing normal non-registered users read-only access so that they can learn about what is going on.

Most clients hide the NICK/PART spam anyways, but yes I have seen that being exploited as well. Isn't there also a channel mode to hide those? That could be combined with the +M defcon mode.

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

No branches or pull requests

3 participants