I gotta admit, I am loving how little of the conversation is just "BlueSky bad! Mastodon good! 🤡" and how much of it is "BlueSky is not ideal for Black users, but let's be for real, neither is Mastodon. We don't have control over BlueSky, but we do have some agency with Mastodon. How can we make Mastodon better? Where are we with improving the issues that make this place unwelcoming for Black users? Clearly, more Black users chose BlueSky than Mastodon. Have we addressed the reasons why?" ♥️🥹

Seriously, I count ~5 conversations in the improvement framing direction. I love to see it! Shame on me for having lower expectations.

I'm unapologetically backing improvements across ActivityPub and ATProto. I back Hachyderm/Mastodon and BlackSky. You can just back both teams! Nothing in the rules says you can't do that!

@mekkaokereke

On the subject of improving Mastodon. This may be an opportunity to rekindle developer attention on the 'Followers Only' dogpiling harassment vector. Felt like some progress on the issue was made back in November, but don't know where it stands now.

cc: @stefan

@mastodonmigration

I wonder if @scottjenson might be interested in connecting with
@mekkaokereke, that is, if he'd like to share some thoughts.

(Unless you two already spoke, in which case, please disregard!)

@mastodonmigration But yes, that particular issue, I have not heard/seen any updates either.

@scottjenson @mekkaokereke

@stefan @mastodonmigration
Yes, @mekkaokereke and I spoke about to how best present Quote Posts and his advice had a direct impact on what we shipped. We're about to reach out for another round of discussions with a wide range of people (but I don't think we've contacted Mekka just yet)

It's so tempting to take the engineering approach and think "this feature will do it!" when we likely need to back up and talk about bigger issues such as culture and moderation.

@scottjenson @stefan @mekkaokereke

It is great to see this conversation take off. You did a fabulous job with quote posts and it would be wonderful if this issue could get the same kind of careful attention. Completely agree that a proper requirements driven approach is warranted. Thank you.

@mastodonmigration always happy to chat

@scottjenson
@mekkaokereke
@stefan

Great. Just to be really clear. What seems to be the issue is a type of hidden dogpiling or 'brigading.'

A tight group folks who's purpose is to harass someone follow each other, 'the brigade'.

One of them composes a harassing post specifically targeting someone who they @ mention, and post it using "Followers Only" reply controls.

The rest of the 'brigade' piles on.

The post is only seen by the targeted person(s) and the harassers.

@scottjenson @mekkaokereke @stefan

There may be other similar issues, but this one clearly seems to be a problem that is often cited.

@mastodonmigration @scottjenson @mekkaokereke @stefan

I think I have client-side improvements for this that effectively hide the harassment.

- https://pachli.app/pachli/2024/11/28/2.9.0-release.html#anti-harassment-controls-for-notifications
- https://pachli.app/pachli/2025/02/28/2.10.0-release.html#anti-harassment-controls-for-conversations-private-mentions

I haven't received much feedback about either, so if you have any, or know anyone who would benefit from these changes, please let me know.

Pachli 2.9.0 released

Pachli 2.9.0 is now available. This release adds additional anti-harrassment controls for notifications, improves accessibility, works around Pleroma bugs, and more.

Pachli

@nikclayton @mastodonmigration @scottjenson @mekkaokereke @stefan

This is a good step, although not enough by itself. Eg the 30 days old filter increases the cost to abusers by forcing them to create and age accounts before using them in order to bypass the filter, which creates a window for mods to detect patterns of sock puppet creation and bulk-suspend them.

Do mods have tools for detecting those patterns of account creation?

@nikclayton @mastodonmigration @scottjenson @mekkaokereke @stefan It would be helpful to support these sorts of filters server side, in a way that can be easily reused by other Fediverse server codebases as well, and/or client-side in other clients.

@david42 @mastodonmigration @scottjenson @mekkaokereke @stefan

True. But also, richer information in the API results would make it easier for clients to innovate around this functionality.

And even without it, it is possible for clients to do this, as Pachli demonstrates. I started this last year because a lot of the online discourse about it seemed to be about how anti-harassment features could only work server-side, which struck me as a significant failure of imagination.