Some instances know their embrace, extend, extinguish history and some don’t.
post
The color codes and symbols aren't at all propagandist.
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.
Oh lol they changed the interface. Just a day ago or so the colours were the opposite.
edit: proof
I thought the same, then I saw the quote at the top of the page and realized it wasn’t strictly for information tracking
Nice, props to whoever made that site.
https://veganism.social/@nm should have added in the desc.
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.
There seems to a mistake saying that Threads is not blocked by lemmy.zip, when we defederated them months ago.
This is not an exhaustive list. For example, Instagram Threads profiles are available from kbin.social, which is not listed here, though.
Am I the one who finds X federated in the status of this website as that instance is not federated ?
It also confuses me that it says like that instance is federated.
Yes. I get the idea, because federating with them is the "negative" option, but honestly it's just confusing and overly opinionated for an infographic.
It's somehow fun to see instance rules adding a clause about We do not federate with organization involved in Genocides
And a pitty that Meta is that Bad !
Is Lemmy.world not going to defederate from Threads? Did I miss something?
Thanks so much for the link!
Time to migrate my account then ¯_(ツ)_/¯
That's Mastodon.world or is that the same as lemmy.world?
What is fedipact?
"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
I hope LW limits federation
Have the admins said anything? Why are we federated with them?
Yep. They don't care and they're going to keep federation with Facebook so "users have the choice to opt out"
Mastodon's largest instance is letting them in too
Good. On one hand it's good to see fediverse stuff coming mainstream, on the other hand the last thing we want is a load of celebrities and brands trying to cannibalise said fediverse as an opportunity to corner the market instead of genuinely useful resources for communication
This is wrong. Rwn.lol blocked threads.net months ago.
top 50 comments