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

NGC: spam protect groups by setting mute for all new peers #2722

Open
zoff99 opened this issue Mar 3, 2024 · 2 comments
Open

NGC: spam protect groups by setting mute for all new peers #2722

zoff99 opened this issue Mar 3, 2024 · 2 comments
Labels
enhancement New feature for the user, not a new feature for build script

Comments

@zoff99
Copy link

zoff99 commented Mar 3, 2024

when IRC freenode network was under attack, all new users and all unregistered users where set to mute be default.
and channel ops gave "voice" by hand to selected users in their channel.

it would be nice to have something similar for NGC groups. that founder and/or moderators can set a group to "mute as default". all new peers would be given the "observer" role.

then moderators can change it per peer, to allow to write to the group.

if someone tries to write spam to a group, and after being muted or kicked then creates new peers to continue to do so, the channel could be set to this mode to prevent more unwanted content written to the group.

@zoff99 zoff99 added the enhancement New feature for the user, not a new feature for build script label Mar 3, 2024
@Green-Sky
Copy link
Member

+1, it would be nice to be able to set a peer's default voice state. Current feature enabling almost the same behaviors is being able to set the group's voice state, which makes it only mod and up or only the founder can talk. (but yes, not the same) or a silencing bot (which can be circumvented).

@JFreegman
Copy link
Member

JFreegman commented Mar 3, 2024

We already have the moderation tools to deal with every scenario you listed. We have voice state to control which roles are allowed to speak (you can set it to MOD so that new peers need to be promoted to moderator before they can speak), and we have the ability to both set passwords and make the group private to limit who can join the group. Users can also use the ignore feature to mute individuals including founders and mods.

The observer list can grow pretty big (in fact I can't remember if we ever purge it at some limit) so it probably wouldn't be a good idea to implement auto-observer-on-join without first resolving that issue. That list gets synced between peers, so limiting its size is important if you're going to be growing it indefinitely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature for the user, not a new feature for build script
Projects
Status: Todo
Development

No branches or pull requests

3 participants