Just to state the obvious:

Any moderation system like Mastodon’s that regularly lets through the kind of sewage that @KimCrayton1 has been highlighting is a moderation system that is failing.

Failing.

Full stop. https://dair-community.social/@KimCrayton1/112872020308883967

Kim Crayton ~ Her/She (@[email protected])

Attached: 1 image And right on cue, the roaches come out Gotta love the originality of the “go back to Africa” comments Just mediocre and unremarkable 🤣😂🤣

Distributed AI Research Community

Spare me the lectures about moving instances, the philosophical underpinnings of federation, “just ignore it,” “I don’t see it,” or whatever excuse you’re halfway through typing.

There’s an old engineering saying: all it’s gotta do is work.

It doesn’t work.

The account in that screenshot appears to be on a self-hosted instance. That is one of the recurring sources of moderation troubles: some new actor can create a pop-up harassment node. Since there’s no instance-level moderation, every •other• instance has to block the account •individually•, which takes time.

(Of course, self-hosted instances are also more vulnerable to attacks of various kinds, and are paying for traffic out of pocket if there’s a DDoS, so…real tradeoff for the trolls there.)

Several replies either asking what the solution is, or proposing one.

Some important context for the posts upthread: We are still at the point where many people are denying that there even •is• a problem with moderation on Mastodon.

The immediate next step here is simply to say, loud and clear, “This is unacceptable.” Let’s not skip that step. It matters.

Beyond that…

…to those proposing solutions: Thanks, keep brainstorming, seek the thoughts of others. There are people who’ve already been thinking about this for a while.

…to those replying in a “How do I help?” spirit: Awesome, please mind the previous post upthread.

…to those inching toward “Don’t complain if you don’t have a solution:” The first step of finding solutions is identifying problems. Denying problems is a way of preventing solutions. Piss off and thx for coming to my TED talk.

My own quick brainstorm for faster, better moderation:

- Reply controls already, like yesterday

- Default to allowlisting for new/unknown instances instead of denylisting

- Federated moderation: option to publish & subscribe to moderation decisions of other trusted instances. Instance owner could (1) fully subscribe to one (e.g. “mirror all of hachyderm’s moderation”) or (2) automatically apply decisions to own instance that multiple other instances made, past some consensus threshold

@Paul Cantrell So you've asked for solutions. Hope you don't want Mastodon-only solutions.

- Reply controls already, like yesterday
How about being able to give general permission to reply to your posts?

How about being able to disable replies to any one of your posts?

How about being able to allow specific followers to reply to your posts?

How about being able to separately allow people to send you posts and to send you DMs?

Science-fiction? Wishful thinking? No, reality. Right now.

Available in the Fediverse (just not Mastodon and not via ActivityPub) for over a decade. Not just yesterday. Since 2012. Invented by @Mike Macgirvin ?️, creator of three federated protocols as well as several Fediverse server apps including but not limited to Friendica, Hubzilla and (streams) and inventor of nomadic identity and the most advanced permissions systems in the Fediverse.

Available on Hubzilla since its inception in 2015.

Available in the streams repository (which he is working on now) since its inception in 2021.

AFAIK, ActivityPub implementation being worked on right now. This means that any ActivityPub project can introduce (streams)' powerful permission settings. These permissions would be understood all over the Fediverse, even between different projects. And they'll go well beyond the above.

Inb4 "The Mastodon devs will be quicker if they whip up something proprietary": No, they won't. Mike is blazing fast, and he has a head-start.

Once he's done, and I hope it's this year, the Mastodon devs must be pressured into implementing it. Even though they didn't invent it.

A Mastodon-exclusive, non-standard, proprietary solution (like quote-toot opt-in) can and will be ignored by the majority of the Fediverse projects because the majority of the Fediverse projects won't implement it, especially if the Mastodon devs can't be bothered to document it for others to implement. Wouldn't be the first time that other Fediverse devs have to reverse-engineer a Mastodon feature.

- Default to allowlisting for new/unknown instances instead of denylisting
Good idea only if the Fediverse was only Mastodon.

Very bad for new or small and obscure projects that won't have a chance to get a foothold in the Fediverse if just about all of Mastodon blocks them by default.

(Okay peeps, now go block me for suggesting something not-Mastodon-exclusive.)

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla #Streams #(streams) #ActivityPub #Permissions #FediverseSafety
Netzgemeinde/Hubzilla