Items tagged with: FediBlock
Content warning: TheBadSpace, Death Threats
Happy Pride! Today, we’re digging into the roots of the fediverse – the many queer, trans, and non-binary people who helped build the Fediverse.
A (partial) queer, trans, and non-binary history of Mastodon and the fediverse
“way back, at the beginning of mastodon’s rise to what it is now, queer activists, be they just a stranger with a keyboard, new to the social media site, weighing in on a topic on the public timeline, or me, someone actively attempting to be the middle between the most vocal voices, and tangible, meaningful change through gargron’s code, and github focused writing and activity, people were queer. they were marginalized, to some extent. people who weren’t comfortable with the status quo, so we changed it.”
hoodieaidakitten, Mastodon’s Complicated Relationship with Queer Activism, July 2018
As a trans woman on the internet, my work with Mastodon has always been about more than just social media—it’s been about keeping people alive.
– Margaret KIBI, Fringe Mastodev – Part II, September 2018
“I cannot count the number of people who I’ve seen and followed…on Mastodon and then come and realize more things about their gender identity, their sexual orientation, their different community markers.”
David Wolfpaw, founder of the tech.lgbt Mastodon community, quoted in Can Mastodon be a Twitter Refuge for Marginalized Groups, November 2022
“Queer people built the Fediverse.”
Christine Lemmer-Webber, co-author of the ActivityPub standard that powers Mastodon and the fediverse, quoted in Mastodon—and the pros and cons of moving beyond Big Tech gatekeepers. In the article, Lemmer-Webber notes that four of the five authors of the ActivityPub standard identify as queer.
Ever since Mastodon started in 2016, queer, trans and non-binary people have helped build it and the interconnected web of decentralized social networks known as the “fediverse.” Today there are dozens or even hundreds of LGBTQ-focused instances,1 and even many of the instances that aren’t specifically for the community are welcoming. Which is good!
People telling the Mastodon origin story usually acknowledges the queer influence. Carl Miller’s Who commands the internet? (from 2018), for example, quotes Mastodon’s BDFL (Benevolent Dictator for Live) Eugen Rochko on the early growth:
“Queer people joined”, said Eugen, “and Furries. It comes in waves.”
Still, very few people I talk to know realize how extensive queer contributions have been – and how much tension there’s been around them. Mastodon: a partial history has a lot of quotes and links to first-person experiences, but they’re scattered throughout it – and it ends in late 2022. So to celebrate Pride, I figured I’d expand on that and also highlight a few of many areas where the impact continues today.
First, though, I want to emphasize that this is a partial history. A lot of people who have made major contributions aren’t here, either because they’d prefer not to be listed (and with queer, trans, and non-binary people under threat everywhere, who can blame them) – or just because I don’t know about them. The names of the people who have made the key contributions have been largely erased. As Sasha Costanza-Chock says in Design, power, and justice:
“[P]eople are often marginalized from the stories we hear about the creation of new tools. Social movements are often hotbeds of innovation, but their contributions aren’t always recognized.”
So my apologies to everybody who isn’t here, and if there are others who should be listed, please check with them if they want to be and if so ask them to let me know.
And speaking of marginalization …
“[T]he first thing that I want to make clear is that Mastodon has a history of being inhospitable to marginalized users.”
Dr. Johnathan Flowers discusses in The Whiteness of Mastodon
In The Whiteness of Mastodon Dr. Flowers focuses on Mastodon’s long history of whiteness and racism, also present in much of the broader fediverse. This marginalization impacts Black, Indigenous, and other queer, trans, and non-binary people or color as well; and many queer, trans, and non-binary people fall into other categories — disabled people, sex workers, people from the Global South — that are also largely excluded from Mastodon’s power structure. As Dr. Flowers highlights, many Mastodonians use the very positive contributions of queer people as a shield against critiques or discussions of the platform racism and overwhelming whiteness. Please don’t do that!
And despite all the major contributions they’ve made, queer, trans, and non-binary people of all colors have also been marginalized in Mastodon. The stories of their contributions are rarely told and when they are it’s rarely from a queer perspective, leading to the erasure I talked about above. And Mastodon and the fediverse have gotten big enough that there’s more and more money and other opportunities floating around. how much is going to queer, trans, and non-binary people? This is something that really needs to change going forward.
And it’s also something to keep in mind when thinking about the history of Mastodon and the fediverse, because it highlights how challenging the environment was for the people making these amazing contributions!
Mastodon’s early days
“When everyone joined there wasn’t per-post privacy or CWs or anything that people associate with Mastodon today. The new wave of queer users came up with, designed, pushed for, and implemented those features.”
– Shel Raphen, former Mastodon volunteer coordinator, project manager, and community manager, in Ana Valens’ Mastodon is crumbling — and many blame its creator (2019)
Rapid queer-led community innovation discusses Mastodon’s first major growth spurt culminating in the breakthrough month of April 2017. Here’s how I summarized it:
Mastodon in early 2017 was hella queer, and the queer volunteers who helped create Mastodon made an incredible amount of progress in the first half of the year
In Mourning Mastodon, Allie Hart links links to github artifacts for the implementation of locked accounts, private toots (as posts were called at the time recently), blocking, muting, and reporting from the time. Conent warnings (CWs) and instance blocking, a powerful technique helping admins and sites protec themselves from bad actors, was also driven by queer and trans people. As I said when discussing this in an April 2017 presentation on Transforming Tech with Diversity-Friendly Software, on open-source projects people can implement the functionality they want and need.
“The recent influx of users to the platform has brought with it new contributors and an expanded revenue stream that has rendered the original nearly obsolete. Queer users could leave en masse without harming the project’s survivability, which means that the reciprocity of their relationship has been terminated — queer users still depend on the project, but the project no longer depends on its queer users.”
hoodieaidakitten has a similar perspective in Mastodon’s Complicated Relationship with Queer Activism
“things changed, because more and more people comfortable with the status quo followed. we queer activists rapidly became the subset that originally came, the marginalized. the minority.”
Things came to a head in The Battle of the Welcome Modal. Many new arrivals (including me) found Mastodon confusing in April 2017. As Valens describes Mastodon is crumbling — and many blame its creator, Shel Raphen – who was doing an outstanding job of project management in a very difficult situation – designed a welcome modal to help with onboarding. Rochko harshly criticized the design and made significant changes that Raphen “broke the pedagogy and curriculum built into the design of the onboarding modals,” which had been reviewed and approved by various other contributors.
Valens describes the incident as “A breaking point for the queer community” and that’s how I remember it too. On the other hand, flawed as it was, the welcome model was also successful, although not as much so as it would have been otherwise: it did in fact reduce a lot of confusion for new users. Unfortunately, progress stalled on onboarding after the Battle of the Welcome Modal, and it remains a problem today.2
Of course, queer people didn’t go away. Creatrix Tiara’s Mastodon 101: A Queer-Friendly Social Network You’re Gonna Like a Lot on Autostraddle later that year brought more queer users, and the number of LGBTQ+-focused instances continued to increase.
And innovation didn’t go away either.
In the private discussions with @bea … I explained that I had actually stopped doing Mastodon development, given my past history with it and the way it had treated its queer contributors. She responded that she had heard that a lot, thought it was sad, and was actually trying to pull together a fork of the software, as a space for queer devs who had been pushed out of mainline Mastodon development. Her focus, she said, was on trans women, and creating a safe place where their contributions would be heard.
Margaret KIBI’s Fringe Mastodev – Part III: Joining GlitchSoc,
The Glitch-soc fork (variant) of Mastodon continued to take the lead in introducing tools to protect users by implementing “local-only posts” in June 2017, an innovation that has since been adopted by other forks like Hometown and most other fediverse software (although still not by mainline Mastodon, so it’s not available on most large instances).3 Glitch-soc also was the first to implement user‐defined profile metadata, collapsible statuses, user controlled layout, and images inside CWs,. Today, Glitch-soc is the most widely-deployed Mastodon fork, and is used by hundreds of Mastodon instances.
Ongoing contributions – often without credit
Queer, trans, and non-binary people continue to make major contributions – often without being credited or acknowledged. A few examples:
- Artist Marcia X created the #FediBlock hashtag for admins and users to share information about instances spreading harassment and hate, and long-time Mastodonian Ginger immediately helped by spreading it to faer networks and normalizing its use. In 2022, this hashtag remains an extremely valuable resource. However, various “fediblock” sites and accounts have popped up over the years without any credit – or compensation – to the original creators.
- In May/June 2018, the initial implemention of trending hashtags – with no ability for site admins to turn the feature off – led to a firestorm of criticism from people who saw it as clashing with Rochko’s claim that Mastodon had “a focus on user experience and anti-abuse tools.” As maloki said, “You can’t have anti-abuse tools by actively creating tools that are very likely to be used for abuse, without consulting people who know and understand anti-abuse.” Cassian’s I left Mastodon yesterday and hoodieaidakitten’s Mastodon’s Complicated Relationship with Queer Activism have some additional discussion. The feature was eventually removed, and an improved implementation was released in 2019.
- August 2018’s Battle of Wil Wheaton highlighted the strength of Mastodon’s LGBTQ+ community in responding to the arrival of a celebrity who had caused a lot of harm to trans people. workingdog_’s Twitter thread provides important context ommitted from most mainstream narratives. Wheaton left the platform as a result, and Rochko posted that he was unhappy with how the situation was resolved. As Nolan Lawson discusses in Mastodon and the challenges of abuse in a federated system, the Battle of Wil Wheaton certainly highlighted the need for improvement in Mastodon’s moderation tools. Five years later, though, the moderation tools haven’t improved significantly.
- Solstice School is a free, online, interdisciplinary conference for the Fediverse, now in its fourth year, hosted by Scholar Social. Past topics include spiders, frugal computing, Afro-Indigenous phenomenology, and data (im)permanence; this year’s topics look just as interesting. As far as I can tell, though, none of the articles about academics exploring Mastodon or the fediverse have ever mentioned it.
- Volunteer moderators are the lifeblood of the fediverse – and a lot of them are queer, trans, and non-binary. Moderation is much more challenging in a decentralized environment, and Mastodon’s moderation functionality is much weaker than is typically found on forums or Facebook, but thanks to the huge amount of effort by (and I cannot stress this enough) unpaid volunteers, some Mastodon sites are so well-moderated that people describe it as a significantly better environment than Twitter. On the other hand, moderators can also be the targets of abuse; in Can Mastodon be a Twitter Refuge for Marginalized Groups, Marcia X describes the harassment campaign— including stalkers, bots, and denial of service attacks – that targeted playvicious.social, leading to the instance shutting down because “our safety was starting to become a real risk and also our mental health for that matter.”
The fediverse is a lot bigger than just Mastodon!
Even though Mastodon has gotten by far the most publicity, it’s only one part of the fediverse. Here’s just a few of the many queer, trans, and non-binary contributors making contributions to other branches as well.
- Daniel Supernault, who’s lead developer on Instagram alternative Pixelfed, one of the fediverse’s most successful offerings, and also started the incredibly valuable FediDB and fediverse.info sites
- Christine Lemmer-Webber, who along with the team at Spritely Institute is developing Spritely Goblins, a distributed object programming environment with time travel debugging and a capability-based model that addresses some of ActivityPub’s biggest weaknesses.
- Kainoa, who’s lead developer on Calckey (a fork of Misskey), which has substantial additional functionality beyond Mastodon as well as a much more vibrant user interface
- Kaity A, who’s lead developer of Hajkey (a fork of Misskey), and along with Ada is admin of LGBTQ+-friendly instances blahaj.zone and lemmy.blahaj.zone.
- The developers of GoToSocial, who are creating a lightweight, customizable, and safety-focused entryway into the Fediverse.
- alyaza, Gaywallet and the other moderators of beehaw.org, who are are using Lemmy link-aggregation software to create a community that “cultivates a sense of real belonging to something” and hosts a very active LGBTQ+ community.
- Hariette, who’s helping to push the Threadiverse to the moon by creating Artemis, a feature-rich, fast, and stunning app for kbin and Lemmy entering beta testing later this month.
https://fedipact.online/, created by trans enby girl lesbian gender terrorist vantablack
As always, it’s interesting times in the fediverse. As Rochko said, it grows in waves. Millions of people created Mastodon accounts late last year in the wake of Twitter’s acquisition by a transphobic, racist, techbro. Some of them liked it enough that they stayed around; quite a few of them are queer, trans, and non-binary – including George Takei, who with over 386,000 followers may well be the most-followed person in the fediverse!
We’re in the middle of another wave right now, with fed-up redditors looking for alternatives in the wake of Reddit’s decision to shutting down third-party apps and ham-fisted response to the protests checking out kbin (an interesting hybrid between Reddit and Twitter) and the aforementioned Lemmy – including people from big trans subreddits which are a critical source of support and knowledge for so many people.
And we’re going to continue to see new waves, because as always, queer, trans, and non-binary people are under siege on other social network. Twitter’s now saying “cis is a slur” and threatening to turn off blocking functionality. Facebook’s parent company Meta is introducing a Twitter competitor then again Anti-Trans Hate Is Absolutely Rampant on Facebook, Transgender Facebook is content dominated by right-wing sources, and Facebook and Instagram parent company Meta’s Nudity Policies Discriminate Against Trans People (as they have for years). So people will keep looking for alternatives.
Speaking of Meta’s Twitter competitor, it’s reportedly going to be compatible with Mastodon, which is another reason it’s such interesting times in the fediverse. As Anti-Meta Fedi Pact creator vantablack says in Why Block Meta?,
try being trans and on facebook, having a list of common suicide methods sent to you by a bigot, and reporting it. they’ll do goddamn nothing. a real, personal, and depressingly common example
Opinions are mixed in the fediverse about how to react to Meta’s potential arrival, but it’s not surprising a lot of trans, queer, and non-binary people don’t want them here. Of course, we’re not the only ones who doesn’t want Meta here; hundreds of instances have already signed the Anti-Meta Fedi Pact vantablack created just a week ago. In FediPact is an Organized Effort to Block Meta’s ActivityPub Platform, vantablack says
I will do everything I can to stop them from burning down the beautiful community we’ve spent over seven years cultivating here.
And she’s clearly not the only one who sees it that way. Still it’s very much in keeping with the fediverse’s history that many of the initial signers of the FediPact are from trans-, queer-, and LGBTQIA2S+-focused instances.
Of course, opinions also differ within queer, trans, and non-binary communities as to how best to respond to Meta’s arrival. As with so many other topics when straight people say “what does ‘the LGBTQ+ community’ think of this issue,” the answer is “it’s complex.” We’re here, we’re queer, fuck Facebook (or whatever they’re calling themselves these days) has more — including a couple paragraphs for allies advocating for working with Meta that are worth repeating here:
It’s a great opportunity to show solidarity. One good starting point is to complement sharing your own opinion with taking the time to listen to, understand, and fairly represent the more marginalized voices who are a lot less likely to be heard – and engage with their criticisms instead of dismissing them. This is especially important for instance admins who want their instances to be seen as LGBTQIA2S+-friendly, employees of surveillance capitalism companies, and cis and/or straight allies with influence in the fediverse.
And allies at surveillance capitalism companies, or instance admins who are allies and have queer and trans moderators, please please please avoid the temptation to rely on your LGBTQIA2S+ colleagues to do the all work or ask them to speak for their entire communities!
One way or another, Meta’s potential arrival is likely to lead to big changes in the fediverse. In chaos there is opportunity! discusses a positive outcome, where resistance to Meta’s arrival catalyzes needed changes in the fediverse. If that happens, we may well see another burst of queer-led community innovation, this time more diverse in other dimensions as well. Perhaps the marginalized people who make key contributions will also get some recognition and more access to jobs and funding. Hey, it’s Pride, might as well be optimistic.
One way or another though, queer, trans, and non-binary people in the fediverse are going to play a big role in shaping the future. Let’s take a moment to appreciate how different this is from the situation on any of the the big commercial social networks! And while we’re at it, let’s also take a moment to appreciate all the queer, trans, and non-binary who have helped create Mastodon and the fediverse as they are today.
1 “Instances” is the term used for different sites that run Mastodon or compativle software. Danielle Navarro’s Everything I know about Mastodon is a detailed introduction to Mastodon; while aimed at data scientists, it’s useful for everybody.
2 Both of the latest attempts to streamline onboarding result in new queer and trans people looking checking out Mastodon signing up by default on the flagship node mastodon.social instead of any of the many thriving LGBTQ+-focused instances. It’s almost like they don’t want queer and trans people to find their community!
3 If you’re thinking that mainline Mastodon’s refusal to support this valuable anti-harassment functionality doesn’t align with the stated values of being a platform with less harassment than Twitter … you’re not the only one. Does Mastodon really prioritize stopping harassment? has several other examples.
Jon Pincus is the founder of the Nexus of Privacy newsletter, author of Mastodon: a partial history, and a software engineer / entrepreneur / strategist and activist who focuses on justice, equity, diversity, inclusion, and intersectionality.
Content warning: fediblock, transmisogyny directed against me
One of their users (presumably the admin) used a report to misgender me personally. The report in-question was over a post I made in reply to their citing of rage.love and weirder.earth in a particular fediblock post of their own:
Using they/them pronouns to refer to me, when I go by she/her pronouns, regardless of any wrongs I may have done is NOT okay and I would advise that anyone who doesn't want themselves or their users to be misgendered in reports stay away from simcha.lgbt as much as possible.
I contacted the admin through this instance's admin email account, demanding a public apology from either that user who created the report, or the admin account within 24 hours. a bit later, I used the admin account to reach out via direct message and make sure they received the email. Zero response. It has since been about 30 hours.
Attached is the report (CW: Misgendering)
Content warning: fediblock, racism, antisemitism, transphobia
With all the other drama going on over the bad space, you may not have noticed that a certain site, minds.com recently added ActivityPub support.
Yeahhh, this one's a pretty easy #fediblock if I've ever seen one
Content warning: fediblock tech[dot]lgbt for racist harassment on top of history of racism and antisemitism
tech[dot]lgbt has had a history of antisemitism and racist behavior as documented by Weirder Earth, before the existence of LGBTQIA+ Simchadon on the fediverse. See this post https://weirder.earth/@WeirderAdmin/109814556541559784. In the following months Tech LGBT claimed to be attempting to make improvements to their moderation to ensure these sorts of situations would not happen again; however, poor moderation behavior from the instance has continued. See https://rage.love/@admin/111042599173615822 for some more information, where Tech LGBT has allowed a user who makes harassing reports to remain on the instance and seems more concerned about that user's safety and giving them another chance than the safety of others on Tech LGBT and the rest of fedi. On top of this, a mod from Tech LGBT kickstarted a racist harassment campaign, and while the mod themselves has shown personal regret for this action the admin of Tech LGBT is still in defense of these original actions. Additionally, we have now found out today that a known racist serial harasser has an account on Tech LGBT; we sincerely hope that this can be addressed promptly.
While we were not around for the original offenses from Tech LGBT, it is clear to us that even if they are trying to correct course − or even if there are members of the mod team who do want to correct course − that this is far from happening. Upon examination of their current behavior and reconciling it with their past behavior over this last year, we are moving to suspend Tech LGBT. Tech LGBT is our biggest source of connections and we will be giving 6 weeks, or until Tuesday, October 24 2023, until defederating.
Content warning: Fediblock tech.lgbt
I recommend a #fediblock of tech.lgbt or at least silence with reports rejected, which is what rage.love currently has in place with suspension being considered. There is an active user on the instance who has abused the report system to send harassing messages that, among other things, concern-trolled about the reported user's young child. You are free to look at the screenshots to decide for yourself on the behavior.
To their credit, tech.lgbt mods have been candid about their process--this user has been warned about their behavior, which they are said to have fully acknowledged as wrong, and will be watched more closely in the future.
Nevertheless, the mods have chosen to retain the user who remains active on the instance. Seeing how the same user or any other could reoffend under tech.lgbt's moderation stance, I recommend at least limiting contact.
(The redaction of the user's account information is at the tech.lgbt moderators' request. For more on this and clarification about rage.love's instance-level moderation of tech.lgbt, see downthread.)
updated Soapblock list for today with 125 new entries: https://github.com/VyrCossont/Soapblock/blob/main/soapbox.csv
note that the only criteria for the Soapblock list is ongoing detection of a Soapbox backend or frontend on the instance domain or one of its subdomains. if you're aware of an instance running Soapbox which is not on that list, please let me know; likewise, let me know if you believe an instance is no longer using Soapbox anywhere and should be removed.
the scanner source will be published when i get around to it, but meanwhile, any entry on the list can be independently verified by anyone by visiting the subdomain mentioned in the blocklist comment.
background: Soapbox is TERF software. the developer, Alex Gleason, is open about his transphobia. he has worked for hate sites Gab and Truth.social to get funding for Soapbox. most of the Soapbox flagship server list has been banned from mastodon.social due to hate speech and/or specifically transphobia, and are also on the Oliphant T0 list. do i really need to paint more of a picture?
to the people who will inevitably respond "separate the software from the author": software is a process with a community attached. it's never just software. Soapbox is a TERF's resume. you run it, everyone knows you've decided to look the other way and work with Gleason and that community for software updates, further enabling hate speech. if you actually plan to fully separate, look to Akkoma's example: hard fork, rebrand, and set a code of conduct.
keep TERFs off Fedi.
Content warning: fediblock, hatred towards Ukraine, anti-Ukrainian slurs on the screenshots
so, @/DarkShy@bronyfurry.com fediblocks us for the reason they should be fediblocked themself
this instance is anti-Ulrainian and they support russian invasion of Ukraine, the rule 7 on their instance is "don't be Ukrainian" (pic 1)
the admin has displayed their hatred towards Ukraine multiple times, there are screenshots, the English translation is put into alt text. they also have Z, the main symbol of russian aggression, in their username
they previously defederated an Ukrainian instance on their Mastodon server because it was Ukrainian
the reason of fediblocking us was because @sarahquartz and I showed up in their replies after all the fascist and anti-Ukrainian sentiments they've posted today, basically because we supported Ukraine here
:NoMeta: #MetaBlock :NoMeta:
For users, mods, admins: Importable #blocklist of #Meta domains: https://drive.google.com/file/d/12pZEz9zMuNyNeJ7y3iK5OIPqn1ALpbwn/view?usp=sharing
For #Fediverse server admins: #iptables commands to block inbound (loads of Threads users) & outbound traffic (like data mining) from Meta's IP addresses: https://drive.google.com/file/d/1lipuAfIC9Q22VClDbTgI_7KZ_aajVZDm/view?usp=sharing
Here's how to #FediBlock your entire server from threads.net (edit: as well as threads.instagram.com, a subdomain of Instagram) on #Mastodon 4.1.0 and above (I'm unsure about how to do this on other #Fediverse #servers, sorry:
FOR MODS AND ADMINS:
1. On Mastodon, go to Preferences > Moderation > Federation.
2. Click "Add new domain block".
3. Type "threads.net" (no quotes).
4. Set severity to "Suspend".
5. Click "Create block".
1. Create a txt document
2. Type "threads.net" (without quote marks)
3. Save as "blocked_domains.csv"
4. On Mastodon, go to Preferences > Import and Export > Import.
5. For input type select "Domain blocking list".
6. Upload blocked_domains.csv.
7. Click "Merge" so threads.net is added to your block list. Do NOT click "Overwrite"!
8. Click "Upload"!
IPv6: 2a03:2880:f231:c5:face:b00c:0:43fe (note "face:b00c")
Looking up threads.net returns #Instagram's logo, the title "Barcelona" and "this page isn't available" (probably because it's not open yet).
peertube dot se belongs to the fascist nordic resistance movement, whose goal is to turn the Nordic countries into a totalitarian nazi state.
Hello !Friendica Admins ,
worth a #fediblock is the domain
*.ngrok.io, it floods the fediverse with
uselesstesting domains, just check these few examples:
I keep you posted if I discover more such domains.
Edit: My first response was like many have fallen into: Woah! That's a spam domain! But it turns out, users can test their (mainly) API code. I'm in contact with the product manager. You can reach him, too.
PSA: It looks like mastodon.social has implemented hCAPTCHA on their signups yesterday.
So, if you have limited / suspended mastodon.social because of the spam issue, you may wish to reconsider this.
This will also likely mean that spammers will move to different instances (already seeing them targeting mastodon.world).
You may wish to consider implementing hCAPTCHA yourself to protect your own instance, and here is the relevant PR:
The reason I'm suggesting this, is because if you are a small/medium instance with open registrations, and spammers find and abuse your instance, I imagine that other instances will limit/suspend your instance without hesitation, given how willing some were to limit/suspend the much larger mastodon.social.
But do note this comment on the PR:
“To give some context to people seeing this: this is an emergency feature backport from Glitch SOC to help mitigating an ongoing spam wave, this feature may not make it in a next release, or with significative changes.”
Edited to add: multiple people have rightly commented on the accessibility concerns with hCaptcha: hCaptcha is really really really bad for blind and visually impaired people.
Please have a look at this excellent reply for more details:
A few examples:
It is already blocked on mstdn.social and masto.ai
Please boost this to spread awareness! ❤️
Note to whoever boosted this Christofascist's introduction where he said he was banned for his opinion without saying what his opinion was:
You MUST ask what the bannable opinion was!!!
Anyway heads up to other mods: I bet Mastodon.Online will ban him soon, so keep an eye out.
reasons: well, harrassment of other users, transphobia and probably even covid denialism (from what i can see and tell from the admin’s account, @ demitasse, at a glance)
seems to also be a single-user instance as there’s only one account showing up when looking up that instance via the Admin-FE (on another instance I’m an admin on)
Let me be shameless for a moment, and say that if you use #fediblock
this would be a great time to tip the 2 babes that started it & got ppl into it.
We do lil things to make communities better that ppl use often and daily.
Show us some love & leave us a tip
She claimed to have killed 309 soldiers.[a] However, many feats attributed to her have been called into question by various historians analyzing her contradictory claims and timeline of events. She served in the Red Army during the siege of Odessa and the siege of Sevastopol, during the early stages of the fighting on the Eastern Front.
After she was injured in battle by a mortar shell, she was evacuated to Moscow. After she recovered from her injuries, she trained other Red Army snipers and was a public spokeswoman for the Red Army. In 1942, she toured the United States, Canada, and the United Kingdom. After the war ended in 1945, she was reassigned as a senior researcher for the Soviet Navy. She died of a stroke at the age of 58.
Early life and education Lyudmila Belova was born in Bila Tserkva, Kiev Governorate, in the Russian Empire (now in Kyiv Oblast, Ukraine) on 12 July [O.S. 30 May] 1916, to Mikhail Belov, a locksmith from Petrograd, and his wife Elena Trofimovna Belova (1897–1972). The family moved to Kyiv when Lyudmila was aged 14. As a child, Lyudmila was a self-described tomboy, who was fiercely competitive at athletic activities. In Kyiv, she joined an OSOAVIAKhIM shooting club, developed into an amateur sharpshooter and earned her Voroshilov Sharpshooter badge and a marksman certificate.
In 1932, she married Alexei Pavlichenko, and gave birth to a son, Rostislav (1932–2007). However, the marriage was soon dissolved, and Lyudmila returned to live with her parents. She attended night school as well as performing household chores. During the day, she worked as a grinder at the Kyiv Arsenal factory.
She enrolled at Kyiv University in 1937, where she studied history and intended to be a scholar and teacher. There, she competed on the university’s track team as a sprinter and pole vaulter. She was also enrolled in a military-style sniping school for six months by the Red Army.
World War II
Pavlichenko in a trench (1942). In June 1941, Pavlichenko was aged 25 in her fourth year studying history at Kyiv University when Nazi Germany began its invasion of the Soviet Union. Pavlichenko was among the first round of volunteers at the Odesa recruiting office, where she requested to join the infantry. The registrar pushed Pavlichenko to be a nurse, but she refused. After seeing that she had completed multiple training courses, she was finally accepted into the army as a sniper and assigned to the Red Army’s 25th Rifle Division. There, she became one of 2,000 female snipers in the Red Army, of whom about 500 survived the war. Although she was assigned a combat role, she was issued with just a fragmentation grenade because of weapons shortages. On 8 August 1941, a fallen comrade handed her his Mosin–Nagant model 1891 bolt-action rifle. Pavlichenko then shot her first two enemies and proved herself to her comrades. She described the event as her “baptism of fire” because that was when she officially became a sniper.
Pavlichenko fought for about 2+1⁄2 months during the siege of Odesa and is credited with killing 187 soldiers. She was promoted to senior sergeant in August 1941, when she added 100 more kills to her official tally. At 25, she married a fellow sniper, Alexei Kitsenko. Soon after the marriage, Kitsenko was mortally wounded by a mortar shell and died from his injuries a few days later in the hospital.
When the Nazis and their Romanian allies overran Odesa on 15 October 1941, her unit was withdrawn by sea to Sevastopol, on the Crimean Peninsula, to fight in the siege of Sevastopol. There, she trained other snipers, who were credited with killing over 100 Axis soldiers during the battle. In May 1942, newly promoted Lieutenant Pavlichenko was cited by the Southern Army Council for killing 257 Axis soldiers. The number of soldiers Pavlichenko is credited with killing during World War II was 309, including 36 Axis snipers.
In June 1942, Pavlichenko was hit in the face with shrapnel from a mortar shell. When she was injured, the Soviet High Command ordered for her to be evacuated from Sevastopol via submarine.
She spent around a month in the hospital. Once she had recovered from her injuries, instead of being sent back to the front, she became a propagandist for the Red Army, where she was nicknamed “Lady Death.” She also trained snipers for combat duty until the end of the war in 1945.
Visits to Allied countries
Pavlichenko (center) with Justice Robert Jackson (left) and US First Lady Eleanor Roosevelt in Washington DC in September 1942. In 1942, Pavlichenko was sent to Canada and the United States for a publicity visit as part of the Soviet Union’s attempts to convince the other Allies of World War II to open a second front against Nazi Germany. When she visited the United States, she became the first Soviet citizen to be received by a US president, as Franklin D. Roosevelt welcomed her to the White House. Pavlichenko was later invited by First Lady Eleanor Roosevelt to tour the US, relating her experiences as a female soldier on the front lines. During the publicity tour, Pavlichenko was not taken seriously by the press and was referred to as the “Girl Sniper.” When meeting with reporters in Washington, DC, she was dumbfounded by the kind of questions put to her. “One reporter even criticized the length of the skirt of my uniform, saying that in America women wear shorter skirts and besides my uniform made me look fat.” They also asked if she used makeup on the front line. She was described by the reporters as very blunt and unemotional in her responses.
Pavlichenko appeared before the International Student Assembly being held in Washington, DC, attended the meetings of the Congress of Industrial Organizations, and made appearances and speeches in New York City and Chicago. In New York City, she was given a raccoon fur coat by Mayor Fiorello H. La Guardia. In Chicago, she stood before large crowds, chiding the men to support a second front. “Gentlemen,” she said, “I am 26 years old and I have killed 309 fascist invaders by now. Don’t you think, gentlemen, that you have been hiding behind my back for too long?” Her words settled on the crowd, then caused a surging roar of support. The United States government presented her with a Colt semi-automatic pistol. In Toronto, Ontario, she was presented a Winchester Model 70 rifle equipped with a Weaver telescopic sight, now on display at the Central Armed Forces Museum in Moscow. While visiting Canada, along with fellow sniper Vladimir Pchelintsev and Moscow fuel commissioner Nikolai Kravchenko, she was greeted by thousands of people at Toronto’s Union Station.
On Friday 21 November 1942, Pavlichenko visited Coventry, England, accepting donations of £4,516 from local workers to pay for three X-ray units for the Red Army. She also visited the ruins of Coventry Cathedral, then the Alfred Herbert works and Standard Motor Factory, from where most funds had been raised. She had inspected a factory in Birmingham earlier in the day.
Having been made an officer, Pavlichenko never returned to combat, instead becoming an instructor and training snipers until the war’s end. In 1943, she was awarded the Gold Star of the Hero of the Soviet Union, as well as the Order of Lenin twice.
Later life When the war ended, Pavlichenko finished her education at Kyiv University and began a career as a historian. From 1945 to 1953, she was a research assistant at Soviet Navy headquarters. She was later active in the Soviet Committee of the Veterans of War. In 1957, Eleanor Roosevelt visited Pavlichenko in Moscow during a visit to the Soviet Union. Pavlichenko struggled constantly with depression because of the loss of her husband in the war. She also suffered from post-traumatic stress disorder and alcoholism, factors that are believed to have contributed to her early death.
Death and legacy She died from a stroke on 10 October 1974 at 58 and was buried in Novodevichy Cemetery in Moscow. Her son, Rostislav, is buried next to her.
A second Soviet commemorative stamp featuring her portrait was issued in 1976.
In popular culture
Second Soviet Union-issued postage stamp dedicated to Pavlichenko The American folk singer Woody Guthrie composed a song (“Miss Pavlichenko”) as a tribute to her war record and to memorialize her visits to the United States and Canada. It was released as part of The Asch Recordings.
Pavlichenko was a subject of the 2015 film, Battle for Sevastopol (original Russian title, “Битва за Севастополь”). A joint Russian-Ukrainian production, it was released in both countries on 2 April 2015. Its international premiere took place two weeks later at the Beijing International Film Festival. It is a heavily romanticized version of her life, with several fictitious characters and many departures from the events related in her memoirs.
The first English language edition of her memoirs, Lady Death, was published by Greenhill Books in February 2018. It has a foreword by Martin Pegler and is part of the Lionel Leventhal’s Greenhill Sniper Library series.
Pavlichenko’s story was featured in the fourth season of Drunk History, where she was played by Mae Whitman.
In Call of Duty: Vanguard, protagonist Lt. Polina Petrova (voiced by Laura Bailey) was inspired by Pavlichenko.
In the 1995 alternate history novel Worldwar: Tilting the Balance by Harry Turtledove, Pavlichenko seems to have been the inspiration for the minor character Tatiana in Pskov.
In the 1944 film comedy, The Doughgirls, Eve Arden played Sgt. Natalia Moskoroff, a highly-decorated Soviet sniper visiting the capital on a good-will tour.
Kate Quinn’s 2022 novel The Diamond Eye is a fictionalized account of Pavlichenko’s life.
TLDR: I’m limiting (followers-only) infosec.exchange for now. In the coming weeks, I and several admins plan to escalate this to a full suspension. Consider migrating if you find the suspensions, and our reasons for them, concerning.
r000t (@ligma.pro, @infosec.exchange, @fedi.site) has been working on a full-text search engine for Fedi for a while:
- Claims to rotate addresses and avoid announcing its presence while claiming that this is protecting user safety somehow.
- Claims that the hourly VPS providers are the top 3 ones used by Mastodon instances, preventing rangebans.
- Teasing a search engine in November with the intention to “specifically bypass all attempts to block it” while branding this as something good for user safety.
- Makes fun of people concerned about such a scraper by comparing them to a Kiwi Farms victim.
r000t released as😛ublic, a full-text non-consensual block-evading search engine for Fedi, after threatening mass violence just days earlier. Previous hint. Went on a bender of threats, slurs, threatening animal cruelty, and eventually posting unmarked gore in an attempt to gain mod attention. See the archived profile for r000t @ ligma.pro when federated to bae.st (CW: NSFL gore). This all happened shortly after admitting to stealing cryptocurrency.
All that infosec.exchange did was limit r000t’s account with a possibility of un-limiting it soon. A mod admitted to receiving several reports against r000t but dismissed them as “fediblock nonsense” while voicing support for this non-consensual engine.
If we assume honesty, then what r000t said about concealing the collector in November would still check out judging by this post made during its release. Also note that the engine does not depend on federation. It uses the streaming API of servers you federate with: as long as you federate with at least one server that the collector is fetching from that has the streaming API enabled, your instance’s posts that federate there can be indexed.
The opt-out mechanism might change; r000t has teased making the opt-out mechanism dependent on federating with ligma.pro.
Unrelated to this fiasco, some more gems I stumbled upon:
- Brags about bypassing authorized fetch.
- Comparing excluding gender non-conforming members of PolyMC to moderating nazis.
- threatening legal action against blocklists.
- bragging about getting away with death threats.
Content warning: FediBlock, LongPost
social.susmaninsurance.com: You’ve seen casino spam, you’ve seen adtech spam. But this is something else: literally just marketing spam for an insurance company. I shit you not. At least they set up their own instance. Check the account “Agent”. Seriously, who do they think is reading this in their chronological timelines?
nekocave.xyz: unmoderated Friendica instance. User “nokitakaze” posts unmarked loli and shota content. Firefox exposes an “image” permission: go to
permissions.default.imageif you really must check.
social.daspr.io: Block the root domain since they also have subdomains like “watch” and “tube” which may refer to a PeerTube or OwnCast instance in the past or future.
- I wonder if this admin is anti-vax.
- Admin bio says “Political refugee that escaped Commiechusetts living in the great state of TX”.
- More anti-vax bullshit from the admin.
- Another user “geoff” posts some anti-leftist suicide memes complete with “clown world” dogwhistles.
- geoff posts “anti-woke” bullshit.
- Oh look, the admin cries about getting censored for COVID denial. Go ahead. Cry some more.
freedomstrike.net: freeze peach COVID denial.
- Sidebar self-identifies the instance as a freeze peach instance.
- Admin “karmaplant” posts COVID denial.
- more COVID denial.
- even more COVID denial.
videos.freedomstrike.org: affiliated with
nalocal519.social: more COVIDspiracy
- Admin “pjd3” follows lots of No Agenda, PodcastIndex, berserker.town.
- Admin posts anti-vax “#plandemic” conspiracies.
- more admin COVID denial.
unperson.us: “if you are easily triggered, this is not for you!” in the sidebar.
- Admin approves of this combo-breaker of a bigotry-laden post.
- boosts COVID denial.
- against abortion rights.
social.epenguin.com: far-right single-user soapbox instance, federates with yikes. The admin “goodtiding5” posts your run-off-the-mill right-wing nonsense:
- posts transphobia.
- COVIDspiracy nonsense.
- “great reset” conspiracy theories from a website known for COVIDspiracy nonsense.
bitcointv.com: PeerTube instance that’s slightly worse than the domain name alone implies.
f.ckpg.space: Relatively new single-user instance.
theapex.social: if you block
noagendasocial.comyou should block this instance too.
- Admin “BenHinc” has a bio which says “a Baronet of No Agenda”.
- Admin mostly follows users on No Agenda.
A few inactive but very yikes small instances:
dissident.business: white supremacy.
- Main page says “Fediverse for White businesses”.
- Admin “mord” has the display name “anti-semitist”.
- Admin profile banner is a confederate flag.
dixies.land: more racism.
- Favicon is a slaver flag (a Confederate States battle flag).
- Locked down front-end but the admin “milk” mains on poa.st.
- Admin “dave” posts Babylon Bee.
- Admin shares anti-vax articles.
- Admin boosts the No Agenda stream.
- Instance also hosts user “irenau” who repeatedly posts pro-life content.
- irenau shills pro-life orgs.
- irenau posts islamophobic content, multiple times.
Just the root domains, for easy copy-pasting:
susmaninsurance.com <a href="http://daspr.io" rel="ugc">daspr.io</a> <a href="http://freedomstrike.net" rel="ugc">freedomstrike.net</a> <a href="http://freedomstrike.org" rel="ugc">freedomstrike.org</a> <a href="http://nalocal519.social" rel="ugc">nalocal519.social</a> <a href="http://unperson.us" rel="ugc">unperson.us</a> <a href="http://epenguin.com" rel="ugc">epenguin.com</a> <a href="http://bitcointv.com" rel="ugc">bitcointv.com</a> <a href="http://ckpg.space" rel="ugc">ckpg.space</a> <a href="http://theapex.social" rel="ugc">theapex.social</a> <a href="http://dissident.business" rel="ugc">dissident.business</a> <a href="http://dixies.land" rel="ugc">dixies.land</a> <a href="http://shadowsocial.org" rel="ugc">shadowsocial.org</a>
Edit: missed a domain in the bottom list.