All of the posts on Mastodon about how the Blue Sky team was silly for releasing a social media network in 2023 without blocking and moderation, even in private beta, and that the Blue Sky team should have known what would happen...

...are being written on Mastodon: a social media platform that in 2023, still doesn't take into account that Black users face a disproportionate amount of very specific types of abuse, and is missing key features that would make the Black population safer. 🙂🙃

It really is the social media equivalent of white folks telling Black folks that Boston is less racist than the South, and completely ignoring any Black folk that live in Boston or anywhere else in the US trying to talk about what their real, lived, experiences have been.

Many Mastodon users are just completely convinced of the superiority of their moderation philosophy, and they are as happy to ignore the few Black Fedi users in 2023 as they were in 2017.

I'm not interested in having Fedi 'splained to me. I'm just saying why more Black folk are on BlueSky:

1. It should be almost impossible for a new, non-technical user to onboard onto the Fediverse and accidentally join a server where they will receive racist death threats.

2. It should not be possible for racists to reply to a Black user's post with hateful gore images, without other users on the server knowing it.

3. It should be easy for a new admin to default into a safe, general denylist.

This isn't an exhaustive list, but these 3 are fairly straightforward ones. And they're not new. You can seriously find Black users asking for these going back to 2017.

Even trying to discuss these often results in:
* You just don't know how the Fediverse works!
* Shared deny lists can be abused, so let's never have them!
* You just love Twitter! You want quote tweets! You want Elon to hurt you again!

So Black Fediverse users tend to self-select into one of a few buckets:

1) Kinda Stubborn (AKA, this isn't my 1st racism): Willing to stay until things improve. People like me, @BlackAzizAnansi etc.

2) Super Stubborn (AKA, I will change you!): Willing to stay and fight the tide of the whole Fediverse for as long as it takes to fix things. @Are0h etc.

3) Normal People (AKA, life is too short): They just leave the Fediverse. This is most Black folk.

The "3s" are going from Twitter to BlueSky.🤷🏿‍♂️

@BlackAzizAnansi @Are0h

If you take one thing from my little thread here it's this: Black people don't leave the fediverse because of openly racist people.

Just like Black people don't leave Boston or San Francisco because of the openly racist people. There are openly racist people everywhere.🤷🏿‍♂️

Black people leave the fediverse, Boston, and San Francisco, because of the behavior of the supposed "non-racist" people. The combination of extreme racism, and denial of its existence, is too much.

@mekkaokereke @BlackAzizAnansi @Are0h I have zero disagreement with any of that but I don’t have enough understanding of BlueSky to understand what makes it better on those fronts?

@iragsdale @BlackAzizAnansi @Are0h

BlueSky is building in 1st class composable moderation providers. FediBlock faced years of resistance.

BlueSky you can see horrible replies. Mastodon, I still run into people that have genuinely never seen the type of abuse that some Black folk endure on the same server that they've been on for years.

BlueSky is starting with just one instance, with curated members, so that you *can't* choose an unprotected server by mistake. Mastodon doesn't have that. Etc

@mekkaokereke What is the guarantee that any new community doesn't take weathering, blocking, and generally nesting? Just the absence of a pre-existing (unwelcoming) community? Will wypipo not go there too?
@acm_redfox @mekkaokereke you wrote "Will wypipo not go there too?" Not sure, but I think the point is that if someone misbehaves they're more easily governable.
@mekkaokereke quote posts coming pronto in @mammoth
@bart @mekkaokereke @mammoth quote posts are available on calckey.social, which is another platform in the Fediverse

@mammoth @mekkaokereke @bart @HannibalElector I’ve been toying with a personal instance of it, and I have to say I am impressed. The original MK is brutal to even try to stand up, as an English speaker. CK in my test env was easy enough to set up and #JustWorks.

I just had a weird backend issue,no SSH on my phone, but pretty sure I can just kill and restart. Has been pretty stable. No idea at scale but I like CK

@bart @mekkaokereke @mammoth Will you consider supporting the “quote" property on status (before converting card / links) which some Mastodon forks (e.g. Fedibird) provide?
@bart @mekkaokereke @mammoth “quote" property follows the same format as "reblog” and includes the full status. Using this property first will encourage more Mastodon-compatible backends to adopt the feature.
@mark @mekkaokereke @mammoth thanks for flagging this! @jtomchak @rileyhBat
@bart @mekkaokereke @mammoth @jtomchak @rileyhBat No problem! I'm currently working on a custom Mastodon-compatible backend designed for single-user instances and have been testing with both Mammoth and Ivory. Here's how quote posts appear on the web & the relevant property in the JSON that triggers it.
@mark @bart @mekkaokereke @mammoth @rileyhBat that’s looking really good. Can you explain or point me to some more details on the ‘quote’ property? Is that just starting with “From:” or “Quote:” before the original status url?
@jtomchak @bart @mekkaokereke @mammoth @rileyhBat Quote is essentially a reblog status that also includes content. Mastodon forks & other fediverse backends include it on the statuses API.
@mark @jtomchak @bart @mekkaokereke @mammoth @rileyhBat oh oh oh. I’m with ya. I was like, wait a minute. How’d you get content into a reblog status through the Mastodon API
@jtomchak @bart @mekkaokereke @mammoth @rileyhBat I think that if popular 3rd party clients add support for the property it can potentially encourage vanilla Mastodon to adopt the feature.
@bart @mekkaokereke @mammoth man how on earth is that the one thing you’re replying to in THIS entire thread
@bart @mekkaokereke yeah i’m aware – you were being a bigoted idiot 6 months ago instead of 6 hours. key distinction lol

@mekkaokereke

Only been here since Nov '22 but I see it too, and it boils my blood. Here's another one:

* Let me passive-aggressively whitesplain how to use the platform while I condescendingly imply there isn't a problem actually and you're just overreacting

@mekkaokereke I'm sure you've mentioned this before, but Mastodon search is terrible, so could you please say again what features Mastodon is missing that would help alleviate abuse Black people face here?
mekka okereke :verified: (@[email protected])

@[email protected] @[email protected] @[email protected] 1) Don't ask Black users to CW discussions of their own racism. 2) Don't be on a server where mods mistreat Black folk. 3) Support the mods on your own server, financially and otherwise. 4) Don't engage with sea lions that say "Mistreatment? Here? prove it!" There have been enough threads shared on Black folk receiving racism. Individually convincing each one is exhausting, and expecting that is a tactic of bad faith actors.

Hachyderm.io

@bwebster @mekkaokereke thanks! That didn't show in my client.

I'm curious about the solutions for these problems that Mastodon could implement and that bluesky is currently implementing.

@bwebster @heathborders @mekkaokereke Maybe I'm dumb but I'm not seeing any features in that post
@mekkaokereke @heathborders @bwebster Thank you for posting this. I didn’t realize this was such a problem and naively thought that the lack of a search function on Mastodon meant there would be fewer racially charged comments and attacks. Thank you for bringing it to our attention and letting us know what we can do.
@bwebster @heathborders @mekkaokereke thank you from the future! Add that to the list: help deflect tiring questions from other white people.

@mekkaokereke his non-exhaustive list of wishes. It's all very reasonable, and I hope bluesky achieves them.

https://hachyderm.io/@mekkaokereke/110273797004251326

mekka okereke :verified: (@[email protected])

I'm not interested in having Fedi 'splained to me. I'm just saying why more Black folk are on BlueSky: 1. It should be almost impossible for a new, non-technical user to onboard onto the Fediverse and accidentally join a server where they will receive racist death threats. 2. It should not be possible for racists to reply to a Black user's post with hateful gore images, without other users on the server knowing it. 3. It should be easy for a new admin to default into a safe, general denylist.

Hachyderm.io
@mekkaokereke Right and so that's the challenge Flowers was talking about. In the two waves of Black folks coming (2017 and now) the reaction on Mastodon sites were the same. He's pointing out this is a cultural problem, not a technical one of moderation alone. How can the community develop in a way where policing how Black people are or communicate stops being the first reaction.
@mekkaokereke Yeah. One of the most difficult lessons in grow-up school is that being surprised does not necessarily indicate that others are incorrect.

@mekkaokereke
Can you explain, please:

1. What is "moderation philosophy"?

2. Are you indicating that black users cannot express themselves on Mastodon as they would like to do?

😘🙏

@mekkaokereke

It seems "moderation philosophy" means the server's criteria used to block or mark certain content, correct?

Also, when following the conversation I sometimes don't know who is meant: only black people or everybody?

@Raven47 @mekkaokereke he has posted this: https://hachyderm.io/@mekkaokereke/109454206758285621 (it’s pinned on his profile btw)
mekka okereke :verified: (@[email protected])

@[email protected] @[email protected] @[email protected] 1) Don't ask Black users to CW discussions of their own racism. 2) Don't be on a server where mods mistreat Black folk. 3) Support the mods on your own server, financially and otherwise. 4) Don't engage with sea lions that say "Mistreatment? Here? prove it!" There have been enough threads shared on Black folk receiving racism. Individually convincing each one is exhausting, and expecting that is a tactic of bad faith actors.

Hachyderm.io

@Raven47 @mekkaokereke Mastodon has its own history with anti-black racism:

https://techpolicy.press/the-whiteness-of-mastodon/

The Whiteness of Mastodon

A conversation with Dr. Johnathan Flowers about Elon Musk's changes at Twitter and the dynamics on Mastodon, the decentralized alternative.

Tech Policy Press

@Raven47

Philosophy: when Black folk say "Can you add this feature that would greatly reduce racism?" We're told "No! That's how Fedi is supposed to work! Just move!" And then moving loses all your posts.🤡

People get more upset about Black people saying Black joy things to each other without a CW, than they do about Black people receiving abuse because they joined the wrong server.

The resistance to safe default deny lists is a trade-off between Black user safety, and fear of being excluded.

@Raven47

@oliphant and @Are0h are better at maintaining a safe deny list than almost any admin on Fedi will ever be. It should be possible for any admin to just delegate responsibility to them at setup time. The decision not to let people delegate and compose ongoing moderation tasks like deny lists, is a philosophical choice that balances user safety (primarily affecting Black folk) with notions of "openness."

(*Even better, it should be possible for admins to pay them for this, but hey.)

@mekkaokereke @Are0h @oliphant @Raven47 That sounds like a feature I've always been strongly in favour of: make it possible to automatically use someone else's block list. That makes people a lot less dependent on admins, who, let's face it, are a fairly limited group with multiple responsibilities. Let people piggyback on other volunteers' moderation.

@mcv @[email protected] @oliphant @Raven47 @mekkaokereke A while back, I saw where someone was working on something like a "Federated" blocklist aggregator - IIRC, the concept was, it tracks which servers were blocked by which other servers, and presented the info as a sorta "reverse social graph", so you can see e.g., who's blocked by everybody, who's blocked by just two other servers, etc.

Seemed like a promising concept! Wish I could find it now...

@mcv @Are0h @oliphant @Raven47 @mekkaokereke on my PC I use dnscrypt-proxy for my network's DNS lookups. This allows me to include a set of merged blocklists provided by dnscrypt-proxy, I get to choose which of them I use. What would be the effect on my merging in one of Oliphant's blocklists on what I see in my browser or an app linking over my network?

@mekkaokereke @Raven47 @oliphant @Are0h Yeah this basically echoes what I’ve been doing with the blocklists I gave Ollie. FediNuke for a baseline, Tier-0 for a starting point with wiggle room, and the full envs list for something more comprehensive. I didn’t even realize this is what I was trying to accomplish until you put it into words for me, in this thread and elsewhere: it should be possible to “stack” these! A sub-network of instances can agree on a minimal list of bad actors, each instance can draw different lines in the sand and hold those lines more comprehensively, and individual users can supplement those with their own boundaries while finding lists that match with them.

One thing I’ll add: blocklists vary when it comes to which boundaries they set, and how well they maintain those boundaries. Understanding the latter is easy but defining the former is probably going to get really messy if our real-time blocklist subscription projects take off.

Edited to link to the article where I describe them.

My Fediverse blocklists

Documentation on which Fediverse blocklists I offer, how they are made, their differences, their caveats, and their intended use.

Seirdy’s Home

@Seirdy @mekkaokereke @Raven47 @oliphant @Are0h

A realtime subscription also has a big advantage over copypasting (which is effectively append-only) in that is makes it possible to federate the removal of servers from a blocklist in the event of a mistake or a temporary problem (after it gets fixed).

@gtsteel @mekkaokereke @Raven47 @oliphant @Are0h YES! removals are an area that’s sorely lacking.
@gtsteel @Seirdy @mekkaokereke @Raven47 @[email protected] @Are0h I wonder if assigning a weight to different blocklists and then using that to decide when to add or remove from your own list could help. Ie weigh servers with shared moderation approaches more heavily than ones with looser/different focus but set a level that reflects your communities’ focus and preferences. (In practice this likely means underweighting blocklists from very big instances but not ignoring them entirely)

@mekkaokereke Could you please reference the issues for the software you are talking about? Mastodon is just one, but not the only one.

What is a "safe default deny list"? Who would be tasked to maintain such a list? There exists a list: https://meta.chaos.social/federation.

chaos.social info

Insights of chaos.social

chaos.social info

@mekkaokereke Having grown up in St. Augustine Florida back when reading about history was still legal in that state, I've got to say kudos for the Boston comparison in particular: https://en.wikipedia.org/wiki/Boston_desegregation_busing_crisis#Violence

The way some of us white folks aggressively forget our histories says a lot about how we'll act when our comfort or self-image are threatened. And that's even before getting to the actual material change we all need!

Boston desegregation busing crisis - Wikipedia