I’ve seen that some instances have already done it preemptively.
For this reason I tend to lean towards defederating because I genuine don’t think your average Facebook user brings much value here - quite the opposite.
I just feel like people don’t quite understand what defederating actually does and I don’t claim to undestand either. However the little that I think I do undestand leads me to believe defederating isn’t going to “cut them out” the way we’re hoping. They can still see all the content here.
From what I understand, if we defederate from them, they can’t see our posts either. See what happened when Beehaw defederated from lemmy.world and sh.itjust.works .
They could still be see the content by creating another instance, or by getting it from lemmy.ca directly. I doubt they’ll do that though, especially with Lemmy. Lemmy communities look weird when seen from mastodon, and I doubt they’d look much better from threads.net.
Also I hate how they called it Threads. That’s already a word used for other things in this space. Theres a thing called the threadiverse, and it doesn’t include Facebook/meta/instagram threads?
Yeah but Beehaw defederated them, not the other way around. If threads.net defederates with us then they can’t see any of our new content but if we defederate with them then the flow of content only stops from Threads to us, right?
Beehaw defederated lemmy.world.
If you go to any community on Beehaw viewed from lemmy.world, you can see that new content isn’t available. Only posts & comments from lemmy.world users show up.
If you go to any community on lemmy.world viewed from Beehaw, you can see the same thing.
As soon as one defederates the other, all communication between them stops, afaik. The content isn’t federated in either direction.
Edit: I might be somewhat wrong, since there are a few posts by users from other instances, but it’s only a few, almost all posts and comments aren’t available. I dont know what’s going on here, disregard what I said.
