Comment on Federated with Threads (or anything meta)
s38b35M5@lemmy.world 11 months agoIt seems unlikely that Meta will federate with Lemmy. When/if Meta adopts ActivityPub, it will likely affect Mastodon only rather than Lemmy, given Meta’s focus on being a Twitter alternative at the moment.
BrikoX@lemmy.zip 11 months ago
Lemmy is federated with Mastodon, so whatever one can see on Lemmy is also available on Mastodon…
Hildegarde@lemmy.world 11 months ago
Just because the servers know about each other, doesn’t mean the users can. Lemmy and mastodon are not fully interoperable. Given the slow and measured development of threads, it will be a long time before they start supporting Lemmy.
BrikoX@lemmy.zip 11 months ago
Again, if the goal is access to content, they don’t have to support Lemmy to be able to pull content from it. They already run several Mastodon instances, but if they started pulling all the content into those instances, everyone would know and block them, but with Threads they can obscure their actions a bit more.
Lemmy’s content is public, anyone can scrape it without federating, the bigger issue is them profiting from that content by federating.
Hildegarde@lemmy.world 11 months ago
But under current versions of lemmy, there is no way to block other instances from accessing data from your instance.
Defederating at this point, won’t stop threads copying lemmy.world content and showing it to their users. All it will do is keep lemmy.world users from interacting with threads content and users.
Future versions of lemmy may allow blocking outgoing federation, but until then blocking threads offers little benefit to the users.
Meta can scrape lemmy data. There’s little that can be done to stop that on a public website. Even if lemmy.world was able to prevent sending any data to threads, they could get it another way.