Issue was closed by Thibault Martin
Issue #480: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/480
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/480
You're receiving this email because of your account on
Thibault Martin commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/480#note_962807
Looks like just something I need to dig on my own :)
I’m closing the issue, thanks
--
Reply to this email directly or view it on GitLab:
Andrea Veri commented:
Is there anything we should do for this issue at this point or it can be closed?
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/480#note_962770
You're receiving this email because of your account
Thibault Martin commented:
As discussed in #opers, the cloak isn’t the route we want to follow because it
can be harder to maintain for IRC administrators.
The best solution seems to be to set an alias to have the following commands
available for room owners:
* `/spamprotect on #channel`
Thibault Martin created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/480
When there are waves of spam on IRC, a popular way to prevent it is to
(sometimes temporarily) restrict access to the channel by adding the `+r` mode
so only registered users can join.
