Alas, the Mastodon spam wave found my instance. Anything I can do aside from turning off notifications?
Conversation
Notices
-
Embed this notice
Filippo Valsorda :go: (filippo@abyssdomain.expert)'s status on Thursday, 22-Feb-2024 10:37:46 JST Filippo Valsorda :go:
-
Embed this notice
Renaud Chaput (renchap@oisaur.com)'s status on Thursday, 22-Feb-2024 10:37:25 JST Renaud Chaput
@filippo We are also working on disabling open registrations if no admin/mod had any activity in the last week: https://github.com/mastodon/mastodon/pull/29318
-
Embed this notice
Renaud Chaput (renchap@oisaur.com)'s status on Thursday, 22-Feb-2024 10:37:26 JST Renaud Chaput
@filippo This will be changed in the next version.
In conversation permalink Tim Chambers repeated this. -
Embed this notice
Filippo Valsorda :go: (filippo@abyssdomain.expert)'s status on Thursday, 22-Feb-2024 10:37:30 JST Filippo Valsorda :go:
Why is the Mastodon default to allow open registration, anyway? It should be a heavily discouraged setting, with moderated signups being the default.
If the moderation team can't keep up with registration requests surely they can't moderate those accounts either.
We've seen this before with open SMTP relays.
In conversation permalink -
Embed this notice
Filippo Valsorda :go: (filippo@abyssdomain.expert)'s status on Thursday, 22-Feb-2024 10:37:38 JST Filippo Valsorda :go:
Thanks for the scripts, but I’m on @mastohost and anyway I can’t run a script every time I want to check notifications.
Turned on the @ivory filter (which got two false positives) and turned off push notifications 🤷♂️
In conversation permalink
-
Embed this notice