- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
This shouldn’t come as a huge surprise. Meta is moving forward with their plans for Theads and the Fediverse, and their adjusted terms reflect a new impending reality for Fediverse users.
You must log in or register to comment.
For all the fucks’ sakes, people.
Yes, Meta sucks. But at least get your shit together before you all start falling over each other to say how these ToS changes mean that Zuck has now given birth to Time Travelling Baby Hitler or some shit.
Meta says, for Threads to federate, they access the same data any instance does when it federates.
And as far as LEMMY.world defederating from Threads… LEMMY. That’s like saying Twitter (or W, or whatever the hell it is now), shouldn’t put Facebook posts in its timeline. Threads is a Mastodon concern. Not Lemmy.
🤦♂️ Ya fuckin’ tinfoil hat nerds. I love you all. But God damn.
deleted by creator
If all you’re looking for is eloquence and footnotes, this person in this post’s comments already has you covered…
https://kbin.social/m/[email protected]/t/410613/-/comment/2032665
deleted by creator
deleted by creator
Can someone please explain why this matters. Almost all madtadon instances are public and can be data mined by any company. Why is it such a large concern if threads is able to see a portion of the posts on the fediverse like any other mastadon instance. To me the only thing threads federation changes is allowing me to view posts on threads without the amount of MS my cursor is over the podt being data mined to know what food Ill be craving in a week.
Everybody, please understand what defederating means. It will not stop the defederated instance from getting the data. It just means you don’t pull theirs.
If you want to actually control who gets data, you’d have to switch to a service like Streams. ActivityPub cannot prevent anyone from pulling data. It only allows an instance to decide not to pull from a specific location.
Everybody, please understand what defederating means. It will not stop the defederated instance from getting the data. It just means you don’t pull theirs.
I’m OK with that. If I wanted to talk to facebook users I’d be on facebook.
Ok, but the number of people that think defederation is in anyway going to prevent this is fairly high.
I see it less about preventing than about sending a clear “DO NOT WANT” message.
I’ve been around since the prevailing attitude across all common internet services was anti-corporate, anti-commercialism. You sound like maybe you have too. We lost that battle. It’d be nice to win this one, even if in a way that matters only to Fediverse users. I know at the end of the day Meta won’t care, and it won’t stop them from slurping up our data.
I still think there is value to the DO NOT WANT message, and when Musk or MS try the same thing, I hope we send the same message to them. Let there be one tiny corner of the internet that isn’t monetized and enshittified to death. Let the users who are happy to use those companies’ platforms use those companies platforms.
I get that this is tangential to your complaint here, and I get it. I don’t care what peoples’ reasons are though. Every instance should support the fedipact, and when Meta finally starts federating I’ll leave my comfy kbin.social home 30 minutes later if it doesn’t.
I hope each new revelation convinces more instance owners to do so, and more users to ask their instance owners to do so.
deleted by creator
Mother fuckers are moving to take ownership of the fediverse by calling us “third party users”.
I’m pretty sure they mean respective to themselves and their own walled garden, but it definitely doesn’t scan well.
If someone had any doubts about federation with Threads, they shouldn’t by now. Facebook is trying to turn Fediverse into Shittyverse and Fedizens should resist that
Defederation means you don’t see their posts. It does NOT mean they can’t see your posts.
I still don’t think federating with them is a good idea, but defederating won’t preserve privacy. It’ll just cut down on the “influencer” BS Meta promotes.
Petition your instance admin to defederate from Threads!
This wouldn’t matter. Defederating means you don’t pull their data, not the other way around.
The article is just describing how ActivityPub works. What would be more important is how they claim to use that data. But that they collect that data is inherent to how the protocol works. They’d have to mention they collect it legally.
Defederation actually does work both ways if the instance enables
AUTHORIZED_FETCH. That setting requires 3rd party systems to prove their identity before they can retrieve any data, which allows an instance to block defederated domains. I don’t know if Lemmy or Kbin supports that, but practically all of the microblogging fedi software does (that being Mastodon / GlitchSoc, Pleroma / Akkoma, Misskey / FoundKey / FireFish, and GoToSocial).Except that means you defederate from everyone but whitelisted instances in that scenario. If I recall, it doesn’t work as a blacklist, but as a whitelist.
You’re thinking of LIMITED_FEDERATION_MODE, which is different from AUTHORIZED_FETCH.
Looking into it, aren’t both of these only Mastodon and not part of ActivityPub itself? I can’t find details on them outside of Mastodon.
And what prevents the post from getting published to other instances from different sources?
They are mastodon-specific, but most fedi software has a similar feature. Or at least, all of the mainstream microblogging software does, as well as some of the image / video sharing platforms. I’m unsure about Lemmy and Kbin. Here are the equivalent settings for FireFish:
Stupid question, couldn’t instances just say they don’t allow scraping specifically from Facebook in their ToS and then report them for GDPR violations if they do?
As in say that have the ToS says that “we’ll give your data to other instances because that’s how the Fediverse works, we won’t give your data to Facebook” and also “Facebook is not allowed to federate, and is not allowed to pull data”.
Then just say that your data subjects don’t consent to any data pulling by Facebook, and Facebook scraping your system even through ActivityPub is a violation of GDPR.
But GDPR is the European thing, and Threads isn’t even available in Europe.
Wouldnt it count for lemmy.world and other European instances because they are from Europe?
Wtf. Can’t they just be defederated. Get that shit outta here.
All instances should start blocking them. Lemmy.world Admins should be on high alert but something tells me they won’t block meta.
Guys, everyone move to small instances so that all the power doesnt go to one instance. I joined aussie.zone just for this reason.
