The Nexus Of Privacy looks at the connections between technology, policy, strategy, and justice. We’re also on the fediverse at @thenexusofprivacy@infosec.pub
Thanks, glad you liked it. Agreed that blocklists (while currently necessary) have big problems, it would really be great if we had other good tools and they were much more of a last resort … I’ll talk more about that in a later installment.
Total bullshit response. Yes, there are a lot of LGBT people on the fediverse. There’s also a lot of homophobia and transphobia on the fediverse. And the instances run by nazis and terfs very much care if you’re trans and will harass you just as much on the fediverse as anywhere else.
It’s tricky … many people do use “queer” as an umbrella term, but a lot of trans people don’t like being lumped under that, and some lesbian, gay, bi, and agender people don’t consider themselves queer. There aren’t great answers.
At some level you’re not missing anything: there are obvious solutions, and they’re largely ignored. Blocking is effective, and it’s a key part of why some instances actually do provide good experiences; and an allow-list approach works well. But, those aren’t the default; so new instances don’t start out blocking anybody. And, most instances only block the worst-of-the-worst; there’s a lot of stuff that comes from large open-registration instances like .social and .world that relatively few instances block or even limit.
If you’re looking for more of a technical deep dive, check out Threat modeling Meta, the fediverse, and privacy
I didn’t say the fediverse has come a long way. I said that many people on well-moderated instances have good experiences – which has been true since 2017. In general though I’d say there was a brief period of rapid progress on this front in the early days of Mastodon in 2016/2017, and since then progress has been minimal. Lemmy for example has much weak moderation functionality than Mastodon. Akkoma, Bonfire, Hubzilla etc are better but have minimal adoption.
And @originallucifer Ipeople have been complaining about this for years – it was an issue in 2011 with Diaspora, 2016 with Gnu social, 2017 with Mastodon, etc etc etc – so it’s not a matter of fediverse software as a whole being in its infancy. Even Lemmy’s been around for almost four years at this point. It’s just that the developers haven’t prioritized this.
If you read the article and follow the links you’ll find plenty of evidence. The Whiteness of Mastodon, A breaking point for the queer community, and Dogpiling, weaponized content warning discourse, and a fig leaf for mundane white supremacy are three places to start.
From the article:
I’m using LGBTQIA2S+ as a shorthand for lesbian, gay, gender non-conforming, genderqueer, bi, trans, queer, intersex, asexual, agender, two-sprit, and others (including non-binary people) who are not straight, cis, and heteronormative. Julia Serrano’s trans, gender, sexuality, and activism glossary has definitions for most of terms, and discusses the tensions between ever-growing and always incomplete acronyms and more abstract terms like “gender and sexual minorities”. OACAS Library Guides’ Two-spirit identities page goes into more detail on this often-overlooked intersectional aspect of non-cis identity.
I’ll get to that in a followon post, but one straightforward way to make progress is to change some of the defaults
As I say in the article:
Despite these problems, many people on well-moderated instances have very positive experiences in today’s fediverse. Especially for small-to-medium-size instances, for experienced moderators even Mastodon’s tools can be good enough.
However, many instances aren’t well-moderated. So many people have very negative experiences in today’s fediverse.
That’s great! And a lot of trans people I’ve talked with on Mastodon say similar things, which is also great. But a lot don’t. It depends a lot on the instance you wind up choosing. So the people who stay wind up as a self-selecting sample.