Made by Nume MacAroon at Veganism.social https://veganism.social/@nm
What is fedipact?
Because the people signed the pact did it long time ago, before any details about Threads federation was known. It was a typical fedi kneejerk reaction.
“i am an instance admin/mod on the fediverse. by signing this pact, i hereby agree to block any instances owned by meta should they pop up on the fediverse. project92 is a real and serious threat to the health and longevity of fedi and must be fought back against at every possible opportunity”
fedipact.online
This makes it just confusing? The pink heart = good, but the red cross = good too? But again the red cross seems bad as green = blocked.
Sorry I don’t get it.
- green checkmark = blocked
- pink heart = blocked, signed fedipact
- yellow exclamation mark = limited
- red cross = not blocked
What about limited, what is it?
You can follow Threads accounts after clicking through a warning.
People who don’t follow those same people won’t see their posts.
You have to manually approve followers from Threads.
Basically, it puts Threads in quarantine, without cutting off all connections.
“i am an instance admin/mod on the fediverse. by signing this pact, i hereby agree to block any instances owned by meta should they pop up on the fediverse. project92 is a real and serious threat to the health and longevity of fedi and must be fought back against at every possible opportunity”
fedipact.online
The color codes and symbols aren’t at all propagandist.
Oh lol they changed the interface. Just a day ago or so the colours were the opposite.
edit: proof
I mean technically, but it’s not like it’s trying to be subtle about it. From the page:
I believe that Facebook represents one of the gravest threats to democracies around the world […]
The point is to discourage instances from federating with threads.
It’s not over yet, friend. There are still things worth fighting for, and still so, so much more we could lose. Don’t give up hope.
This is not an exhaustive list. For example, Instagram Threads profiles are available from kbin.social, which is not listed here, though.
On kbin/mbin you can look at https://<instance>/federation it has a list of known instances and right at the end is the list of defederated ones.
Huh. You’d think more instances were blocking, given the amount of buzz.
Being generallky in favor of letting individual users make this call that’s… mildly encouraging. Of course I happen to be in an instance that is blocking, so…
It’s worth noting that this still splits Mastodon pretty much in half. That’s arguably a bigger concern than anything else Meta may be doing. They may not even have to actually federate to break Mastodon, which is a very interesting dynamic.
Oh, hard disagree on the last part, at least.
As always in left-leaning spaces, the best way to disarm any threat of reform is to wait for whatever purity test over a random issue to trigger a schism, sit back and watch. It’s not even the first time it happens to Mastodon specifically.
In this case, a potential competitor that already has a reputation for being overcomplicated and having bad UX now needs an extra FAQ item called “can I interact with Threads from Mastodon?” and the answer is “it depends”.
It’s terrible, self-destructive and worse than either a yes or no call. Zuck boned Masto by federating a handful of employee accounts only AND he’s still going to get the plausible deniability in front of regulators from federating with whatever’s left. I’d be impressed if I thought Meta did it on purpose instead of it being entirely self-inflicted.
Thanks for putting this in words, I had been struggling thinking about what was bothering me about this.
