Threads is automatically hiding comments that mention Pixelfed
mastodon.social
For anyone wondering if Threads and Facebook at large will be a fine neighbor in the space and compatible with other apps/services in the fediverse: they’re already automatically hiding comments that mention Pixelfed https://mastodon.social/@dansup/112126250737482807
You are viewing a single comment
Serious question: how do we - the end users - stop federating with Meta?
Move to an instance that won't.
Burying your head in the sand doesn't change the fact that whatever LW does will affect all of Lemmy. They're too big.
That sounds like a problem for instances federated with Meta. Empathy is cool but they are not our problem.
This is a strange response for me because de-federating is an active step on behalf of its admin, usually after a vote amongst its users, at creating a virtual boundary between the two entities. How is that burying your head in the sand? And yeah, lemmy.world is big, but aside from the obvious loss of content/users, what other effect will that have on the mass of de-federated instances?
Someone correct me if I'm wrong, but my understanding is that since LW will federate with them, any content they host, will end up on meta.For example, this discussion we're having right now is on !technology@lemmy.world. So it doesn't matter whether our own instances have defederated meta - our posts and comments here will bring them value. Directly, in the form of content. And indirectly, in the form of processable data for machine learning, shadow profiles, etc.Your understanding is wrong. Instances don't forward stuff from other instances to other instances. Instances only send their own content directly to the instances they federate with.
Thanks!
So on a different instance that's not federated with Meta I can see LW content but not Metas?
Yes
Uuuh no it won't? The fact that they federate with Threads doesn't mean that my instance does. How does it affect me?
You posted this to a LW community, so your content and data will end up in Meta's hands as well.No, that's not how federation works. My instance sends my content directly to everything my instance federates with. No instance takes content from other instances and sends it further - that is not a thing. I sent my content to lemmy.world and it is free to be there. Lemmy.world will not forward that to Threads.
Migrate away from instances that embrace Meta to those that do not. Choose an instance that aligns with you.
Or in the extreme case, if you're the first who can't find such an instance and you're technically inclined, there's your room for a new instance. It's how the fediverse works and partly why Meta is so intent on destroying it.
How does one find a list of instances that aren't federated with meta?
Replied in another comment, but here is is again. https://fedipact.veganism.social/
Appreciate the link! Glad to see that both my mastodon and lemmy instances have already blocked their content.
What's the difference between blocked and fedipact?
The tooltip for fedipact says: "Agreed to block all communications (their blocklist is private)"
To me that says, they've agreed but it's not confirmed that they've gone through with it because the blocklist is private. Blocked on the other hand says "All communications are blocked"
Thanks! I was on mobile and couldn't see the tooltip
I think fedipact actually sign the pack to block and the others just blocked.
Thanks for this. Looking to make an account on a better server now
I don't know,but you can check individual instances by going to the/instancessubdomain and searching for threads.shjw and blahaj are defederated, world isn't.
This can always change, but I have confidence in my admins.
Edit: Thanks to Canyon201@lemmy.world for this link
EDIT: removed comment due to outdated and inaccurate information.
Not sure anyone posted this in direct reply to you - https://fedipact.veganism.social/
You can search/filter for your instance there. As an example, if you search lemmy.world you'll see they currently do federate with meta.