It should come as no surprise that the lemmy.ml [http://lemmy.ml] admin team
took about 2 minutes to decide to pre-emptively block threats / Meta. Their
transparent and opportunistic scheme to commodify the fediverse and it’s users
will not be allowed to proceed. We strongly encourage other instance
administrators to do the same, given the grave threat they pose to the
fediverse.
You’re confusing something. Defederation by lemmy.ml means that lemmy.ml users cannot see any threads.net content if they wanted or not. Threads.net can still connect to lemmy.ml. That’s exactly the situation lemmy.world and beehaw.org are in: beehaw.org blocked lemmy.world and lemmy.world users can see and interact with everything from beehaw.org, just beehaw users don’t see any of those interactions. Have a look at https://lemmy.world/c/[email protected] as proof.
So many folks on here are jumping on and claiming that decentralization is a one way or that people don’t know anything, but have failed to read the specifications themselves.
ActivityPub defines the Block activity for client-to-server (C2S) use-cases, but not for server-to-server (S2S) – it recommends that servers SHOULD NOT deliver Block activities to their object.
So as I mentioned before, Lemmy.world should be blocking those servers at the instance level, preventing it from sharing any data to any identified Facebook instances.
Sure this doesn’t stop Facebook from spinning up other instances, but that will improve a lot more effort on their side and will quickly be identified and blocked by the communities, just like all their urls for ads, api, etc. have been for years.
but have failed to read the specifications themselves.
What the specs say doesn’t matter if reality behaves a different way. Fact is that Beehaw blocked Lemmy.world but not the other way around and therefore Lemmy.world users can read everything from Beehaw. Lemmy.world blocking Threads would thereby be at best just a symbolic gesture and at worst actively driving people away towards Threads because that’s where they can access all the content. If an e-mail provider blocked all mails from @gmail.com, most of its users would jump ship towards a provider that doesn’t do that and perhaps even drive them towards GMail.
It does actually matter, because that is what is happening.
Head over to the [email protected] link that you shared as an example and notice that the posts are 3+ days old and all the recent posts are from instances other than beehaw; this clearly shows that Lemmy.world has not been receiving any data from beehaw for some time already.
As for hurting Lemmy and driving people to threads, is a baseless argument; anyone wanting an experience that Threads offers is not coming to Lemmy; they would either already be there or would be coming from Twitter/Mastadon.
Lemmy at its core is very far from what Threads/Twitter/Mastadon try to be.
3+ days old and all the recent posts are from instances other than beehaw; this clearly shows that Lemmy.world has not been receiving any data from beehaw for some time already.
The block is older than three days.
anyone wanting an experience that Threads offers is not coming to Lemmy
It would not be that simple, considering they’d be running multiple instances and require more effort to aggregate, deduplicate, and stage that data - vs just having a single clean database for it
Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: [email protected]
Facebook is known for analyzing your contact list and trying to get as much data as they can on those people as well. You don’t have to make life easier for face-eating leopards.
This data is public and anyone can just write a crawler.
Anyone can do anything; the point is handing it over automatically and neatly into a database and ready for use.
You’re confusing something. Defederation by lemmy.ml means that lemmy.ml users cannot see any threads.net content if they wanted or not. Threads.net can still connect to lemmy.ml. That’s exactly the situation lemmy.world and beehaw.org are in: beehaw.org blocked lemmy.world and lemmy.world users can see and interact with everything from beehaw.org, just beehaw users don’t see any of those interactions. Have a look at https://lemmy.world/c/[email protected] as proof.
So many folks on here are jumping on and claiming that decentralization is a one way or that people don’t know anything, but have failed to read the specifications themselves.
https://www.w3.org/TR/activitypub/#block-activity-outbox
https://docs.joinmastodon.org/spec/activitypub/
So as I mentioned before, Lemmy.world should be blocking those servers at the instance level, preventing it from sharing any data to any identified Facebook instances.
Sure this doesn’t stop Facebook from spinning up other instances, but that will improve a lot more effort on their side and will quickly be identified and blocked by the communities, just like all their urls for ads, api, etc. have been for years.
What the specs say doesn’t matter if reality behaves a different way. Fact is that Beehaw blocked Lemmy.world but not the other way around and therefore Lemmy.world users can read everything from Beehaw. Lemmy.world blocking Threads would thereby be at best just a symbolic gesture and at worst actively driving people away towards Threads because that’s where they can access all the content. If an e-mail provider blocked all mails from @gmail.com, most of its users would jump ship towards a provider that doesn’t do that and perhaps even drive them towards GMail.
It does actually matter, because that is what is happening.
Head over to the [email protected] link that you shared as an example and notice that the posts are 3+ days old and all the recent posts are from instances other than beehaw; this clearly shows that Lemmy.world has not been receiving any data from beehaw for some time already.
As for hurting Lemmy and driving people to threads, is a baseless argument; anyone wanting an experience that Threads offers is not coming to Lemmy; they would either already be there or would be coming from Twitter/Mastadon. Lemmy at its core is very far from what Threads/Twitter/Mastadon try to be.
The block is older than three days.
So no need to block them then.
Sounds like you’re really missing the threads experience; why aren’t you there and posting 250 characters at a time?
Same reason I don’t use GMail and yet want to keep the option open to receive and send e-mails to GMail users.
It won’t be a lot more effort. They’d just have to buy another domain and then suddenly bob is their uncle.
It would not be that simple, considering they’d be running multiple instances and require more effort to aggregate, deduplicate, and stage that data - vs just having a single clean database for it
Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: [email protected]
Facebook is known for analyzing your contact list and trying to get as much data as they can on those people as well. You don’t have to make life easier for face-eating leopards.