Also since that resulted in mstdn.social being listed, I've had to yeet it from said recommendation list for #ActivityPub :activitypub: instances in the #Fediverse :fediverse: ...
I would love a list of servers who have activated authorized fetch, because ultimately not being associated with facebook, twitter etc is more important to me than making it easier for people with friends still using those services to see those posts. #AuthorizedFetch exists and if it means paying my instance every month to be part of something I can feel good about as opposed to feeling like I am complicit in the crimes commited by facebook and twitter, I would happily do that. #Fedipact#AskTheFediverse
What if the real #Fedipact was that the whole #Fediverse exclusively set AOL.com as their homepage and used AOL for all their web searches from now until 1st January 2024 to really confuse #AOL employees when they returned back to work. They'd think it was 2001 again.
@007#FediPact is about moderation and protecting users from known harm, and about prioritizing marginalized peoples' safety over privileged peoples' reach. There are lots of servers like that don't block any others no matter how much vile and hateful content they host (such as #Threads). But worth pointing out that most of those have already been limited and/or blocked by those servers who do take moderation responsibilities seriously.
@Amelia@007 I really want to know why so many threads.net apologists talk abstractly about being against the "general concept of blocking" or how they want to "let the users decide" but are somehow mysteriously okay with instance-level blocks of poa.st
I suspect the real reason is either
a)They simply haven't thought about it. Maybe some mastodon.social users aren't even aware that their instance blocks over 200 other instances.
b)They actually want to give threads preferential treatment compared to other Nazi instances, possibly due to it's size. Any vague Freeze Peach or "open federation" arguments they make are therefore in bad faith.
But it's possible there's another reason I can't think of, and that's why I keep posing the question to creatures like @007 : why do they want to give threads preferential treatment?
Regardless, I'm glad to be on an instance that's blocking threads.
@nm Also focusing on threads alone might help creating the impression, that every "bad actor" (supposedly or not, it doesn't matter in this discussion I'm trying to make) has to be singled out and be blocked into oblivion, which creates nifty pathways for trolls to cause havok.
If a had a last request, in case you want to expand: Many do blocks and never think of them anymore, only some do the due diligence and re-assess their blocks. We need a way to show possible outdated information.
@nm I want this to become actually helpful in managing someones own instance, and not to become a tool to block each other until there is no federation anymore (the benefactors would only be sites like threads).
Did you know that, if you or your Mastodon instance is blocking Meta, your posts and account can still be data-mined by them? That is, unless your instance has Authorized Fetch activated. More info here: https://kolektiva.social/@ophiocephalic/111602259275182233
“I believe that Facebook represents one of the gravest threats to democracies around the world, and I am amazed that we have allowed our freedoms to be taken away by technology companies’ greed for growth and revenues.”
Maria Ressa, How to Stand Up to a Dictator, 2022
#Fedipact - The instances blocking Zuckerberg's Threads.net
With the Zuckerberg takeover impending, there's a lot of confusion circulating about the use of user-level and instance-level blocks, and how our online expressions can be secured against Meta. Everyone who objects to their accounts being mined by the Zuckerberg entity for data collection, AI ingestion, monetization, and possible ghost-profile building needs to understand this problem. Here's information to clarify.
Neither a user-level block, or an instance-level block, will protect our posts from Meta data-mining by default on a Mastodon instance. Posts won't be delivered directly, but can be ingested by other means; if, for example, users on Meta-federated instances boost them.
However, both user and instance blocks will totally prevent post delivery in all cases IF your host instance has enabled the functionality called Authorized Fetch.
By default, Authorized Fetch is off on Mastodon instances and most haven't turned it on. If this concern is important to you, you might want to respectfully reach out to your admins and let them know. Remember that they are working hard to provide and sustain online community at no charge. It's likely they won't be very familiar with it and will need time to look into it.
@rotfarm i dont think threads would be able to see ur stuff just because flipboard federates with them. unless they're sharing user data with each other intentionally.
My 2 cents: I'm good with you holding off, taking a wait-and-see approach to Meta federating, as an instance admin.
But I want you to know why I'm blocking the entire Threads instance: I do not expect them to adequately moderate hate and misinformation. I don't want trolls and agitators in my feed.
I'll be watching what happens. I hope you will be too. :-)
@deborahh@chad That’s my thought as well. It’s not like Threads is a dedicated nazi instance that should be immediately blocked, there will most certainly be people there wanting to offer up good conversation, but I’m skeptical of the corporate intentions involved. I’ve blocked them as well, but may eventually check to see if old Twitter follows migrated there.
#fedipact Says it will block #Meta#Threads https://fedipact.online/
People fear that it will "split" the Fediverse.
But it will only do what a net does, nodes and subgroups not being connected to everyone else on the net.
That already happens by usual blocking.
I think I would look at what comes from threads but I understand everyone that will block.
"Everyone has the right to freedom of peaceful assembly and association. No one may be compelled to belong to an association."
The #fedipact is a declaration of solidarity together. But it's not compulsory. Those instances are exercising their FOA rights to not to be compelled to federate with threads or any instances they don't want to.
There are some hot and appropriate takes going around about the "leadership" at the top of major fediverse projects, and its imminent failures. One of those leaders literally describes himself as a "dictator". Well, now his technology has a new dictator, one who has no credible pretense to benevolence.
It seems there are two kinds of FOSS-folk among us. One contextualizes their technical work with a political understanding; be it anarchism, socialism, or some variant of an oppositional outlook, which posits FOSS in an anticapitalist, antiracist or liberatory context. They know there's something out there to stand against, and aspirationally, replace. I salute them and hope we can all build together.
The other, while more-or-less into FOSS, seems to be motivated by nothing deeper than a "tech is neato" ethos. One could argue that it's this second type that has brought us to the crisis.
If tech has any chance to facilitate liberatory - or even alternative - agency (and it's arguable if that chance exists), it has to be about something more than itself. As we watch ActivityPub, Mastodon and Pixelfed get recuperated into the Zuckerverse, here's hoping we can figure out a way to sustain and support those developers of next-gen decentralized and peer-to-peer social networking who understand this
@ophiocephalic@nm gonna give a shout out to GoToSocial devs, as people I think embody this. It’s not a fork, it’s in alpha, but it’s compatible with everything and it’s sweeeet
@meljoann@nm
Agree, that is definitely one of the most interesting prospects on the horizon! Bonfire, with its strengths in organizing groups, is also very intriguing
@onepict
Yes, but those "small communities" make big block lists, that affect small, medium and large instances, based on gut-driven decisions the major part of the time, not giving reasons or making them automated, with the "guilt by association" directive
Ok, I didn't get the #fedipact before, but in just a few hours on #threads I saw so much problematic content that I now totally get the point.
For languages besides English Metas moderation is just non-existent.
In the past I've reported ig comments that directly threaten queer people with violence and the response has always been "we don't see any reason to take action".
