Gregory's Server@homegrown if you imply people should block open registration servers, I'd say this is bordering on fud. Closed registration is a significant hurdle for some folks and a lot of serverteams are doing gods work to monitor signups closely to be able to keep their registration open. Please don't imply otherwise.
|
10 comments
@homegrown after the fact? Sure, I'm with you and do that myself (and always temporarily close our registration as soon as we're aware of a significant wave). The point is I see a disturbing lack of nuance, when it comes to asking to get rid of the option or even preventive blocking of servers that offer it. They're not all abandoned hellholes. On the contrary.  @dnddeutsch @homegrown @dnddeutsch @homegrown I mean they're clearly not - I've submitted reports of 11 spammer accounts across eight instances in the past few hours this morning, each one of those accounts has spammed *at least* 20 users (20 is the maximum number of posts we can check to report as 'evidence') - if a user on your instance is able to get THAT far with spamming, it's already too far and you are not able to effectively moderate open signups. @dnddeutsch @homegrown Meanwhile, moderators on other instances are getting bombarded with reports of the source instance's spam problem and we're having to deal with it to protect OUR community from spam because THOSE instances are not doing a good enough job. All our mods - most mods of instances across the fediverse - are unpaid and voluntary. It's Saturday morning, I'm not getting paid to sit in front of the report queue sniping spammers for the past four hours because another instance - @dnddeutsch @homegrown - cares more about increasing their number count than providing a safe space for not just *their* community, but all the other communities connected to them. The server teams 'doing gods work' are the ones who've responsibly turned off open sign ups and are still having to moderate spam from other instances who haven't. @dnddeutsch@mastodon.pnpde.social @homegrown@social.growyourown.services it's not FUD - blocking open-reg servers was the most effective solution to that first Misskey spam wave a while back. My co-admin actually wrote a script to do it automatically, and it helped so much more than any filter we applied.  @dnddeutsch @homegrown that's what happens though. We've silenced a shitton of instances who had their registrations open and were overrun with spam bots as a result. Manually approving signups is trivial. If that's too much of a hurdle for users, that they may have to wait for a day to get approved, then they need to learn some patience. @dnddeutsch @homegrown when you rent an apartment, you can't move in immediately. You have to pay a deposit, you have to clear a credit check, etc. When you join a club or political party, you aren't a member immediately, a human has to approve your application for membership. "Arrives the next day" shipping from Amazon and corporate social media has made people impatient, but historically, very few things happened instantaneously. Instant gratification is a very, very recent phenomenon. |
@dnddeutsch
I'm not saying they should, I'm saying they will.
If someone's server is overrun by hundreds of spams from an ever-changing set of spam accounts on a remote server, and the remote server isn't doing anything about it, what other options are left other than blocking the remote server?