Wildeboer’s third theorem: Every commercial centralised service that offers “free” services and relies on ads and/or a percentage of subscription/donation fees ends up being supportive of misinformation, hate speech and far-right to nazi content. Either through ignorance or acceptance.
"Woke" is an English word. But its usage to mean "alert to the dangers of prejudice and systemic racism" is a Black American invention.
Its evolution into a pejorative encompassing everything right wingers don't like is literally a white supremacist fascist plot to attack the progress of e.g. #BlackLivesMatter.
Sascha probably thinks of himself as progressive or something along those lines, but here he is just a puppet whose strings are being pulled by DeSantis, Rufo, RT, and the rest of the right wing fearmongers.
In a test environment (with a separate VM spun up on a private non routed VLAN on a simulated network) I tested removing the umpteen-gajillion servers from the do-not-federate list (moderation/federation) using multiple methods.
Using SQL to remove all records where a particular server name was listed caused mastodon to refuse to start - at all. I ended up deleting that VM. (this VM never touched the internet - it lived in a simulated network (a VLAN dedicated to experimentation) which had no access to the real world)
My attempt at writing a script to automate the removal via API flopped. Either 401 errors or corrupted requests which did something, but I couldn't tell you what... but the copied instance decided it didn't want to play nice - even after my letting it sit for an hour to let the database catch up.. Web access to the instance was iffy, at best.
I'm at a loss. I need to find an easy way to clear out this 25-page list of servers which I should have never added in the first place without mangling my instance.
For the record, I am all in favor of different people and groups developing their own shareable #blocklist for the Fediverse.
For let's be frank: Easy blocking of bad actors is essential for any kind of useful or enjoyable social media experience, and we can't just leave this task to individual admins and expect them to cope.
In its final years, I used the LikersBlocker Chrome Extension to block hundreds of thousands of accounts on Twitter, which was the only thing that kept the Twitter experience remotely bearable. And when the Twitter API was shut down earlier this year and the extension no longer worked, it was just one more nail in the coffin for this platform for me.
And we aren't ever going to develop a common consensus on who or what constitutes a "bad actor" who should be blocked. And that's okay! It's far better for multiple groups to develop their own consensus, and then every user and every instance can use the blocklist of people they trust.
If for whatever reason you never wish to interact with #Threads, you can personally block it for your account. This hides all posts and profiles from Threads, prevents anyone from Threads from following you, and stops your posts from being delivered to or fetched by Threads. Simply click the "Block domain threads.net" option on any Threads profile or post you see in Mastodon.
Grab the file from GitLab and remove the line “Known Meta Sites:” Then, use spits on ground Excel or LibreOffice or e.g. https://convertio.co/txt-csv/. Or (on macOS at least), just change the suffix.
When done, download the .csv and go to your profile settings. Now go to:
Import and export > Import > Import type [important!] > Domain blocking list > Merge [important!]. Click UPLOAD and you're done.
Note that it'll take a while until your #blocklist has been processed.
this account is automated art theft and I'm disappointed in those of you who engage with it. It seems transparently aimed at eventually turning other people's work into clout & the clout eventually into cash. There's nothing sincere behind it. #BlockList
Anyway the art in this reminds me of the style of person who does series like "A month of anarchist ferrets" and every day in October they'd draw colorful cute ferrets saying going #ACAB or something like that. Bold colors, childlike crayon strokes. (I think they're even on the #Fediverse. If you know who I mean, please tell me!) This is so unnecessary. Curation is wonderful but it's work when it's done correctly and this isn't. #Anarchist#Anarchy#community#art#artists
Since Threads & Fedipact are the topics of conversation: If you don't want to deal with a Zuck-loving reply guy who thinks instances publicly stating their intent to block #Threads is basically fascism then probably block this guy #BlockList#FediPact
It seems like it's not the UI or the usability, that get's people to leave #Mastodon nowadays but - small, yet vocal and totally not self-critical - parts of the community, that can't stop lecturing others about the #Fediverse and how to act/post/comment here or about what.
German Mastodon had the ridiculous debate about #Zoom, other parts similar stuff (scolding someone for #bw-photos... really?).
Maybe the recent update helps people get it together, otherwise it will get even quieter here.
@mho Some folks are just assholes that want to dictate others how to post instead of pressing #mute and/or #block button if they can't handle someone...
But then again we see Egoists like #Ro abusing his #blocklist (#TheBadSpace) as a tool for personal vendettas and to silence critics, so I'm not surprised about it...
Since the beginning of this year I've been maintaining a Mastodon server blocklist called Garden Fence, available at https://gardenfence.github.io/
As the Discord admin space that was being used to coordinate with other admins on the list has since closed, I've set up the account @gardenfence to pick up communication and notifications around the blocklist.
In particular I hope to expand the list of volunteer reference servers in the near future to replace a server that plans to leave the list, to keep the list at a reasonable size.