Lemmy.ml has now blocked threads.net / Meta
(lemmy.ml)
It should come as no surprise that the 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.
meta is trash and we don’t want its data getting all snuggly with ours. because ew.
now you’re up to speed.
edit: data privacy concerns are the main issue
Our data is already public though? The ActivityPub standard specifies that the majority of data we publish on any given instance is public through that instance's API, and a web scraper could be easily built that would comb through and gather all of it for advertising or machine learning purposes. The only real way to avoid that would be to take the sites themselves private, which would kind of defeat the point of social media, or to just not use social media.
This private data
is what Threads is after.
And, no, it’s not “already public.” Or, for your sake, I hope yours is not. Mine certainly isn’t, and I don’t want it to become so.
Oh yeah, the app is a monster that will eat all of your data. I thought we were talking about federated data they would get from the other instances, which is more or less public. My data as shown in that image is not public and I have no plans to hand it over to Meta.
well… you make a point that everything that you post on the internet is “public” in a sense, but there’s a pretty big difference in the effort required to scape it and providing direct API access to the data source which gives Meta access to much more than simply the contents of a post.
think of it as the difference of bing able to get a blood donation and sticking an IV directly into another person’s (or, in this case, anyone’s and everyone’s) artery, unfiltered, anytime, every time, on-demand, and without permission. forever.
no thanks!