- cross-posted to:
- fediverse@lemmy.world
- cross-posted to:
- fediverse@lemmy.world
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 # to comment.
Provided that a Third Party User is followed by or following a Threads account, Meta will ingest these pieces of data specifically:
Username
Profile Picture
IP Address
Name of Third Party Service
Posts from profile
Post interactions (Follow, Like, Reshare, Mentions)
So if you follow a threads user or even if a threads user just follows you, they pull all this data?
IMO this seems like reason to defederate across the board. Someone else can leak your info to Meta.
Question, is this not how every activitypub server works?
Isn’t this just public information anyway, what’s the problem with them taking it?
It’s Meta. This is just the beginning. Stop them right from the start. Fuck these corporations.
How does defederating them stop them from getting this public information if they want it?
Good point. I guess they could just fire up a shell instance and get all the good stuff. I wouldn’t be too surprised, actually.
They don’t even need an instance to get they can just scrape it, like anyone can with public info. They wouldn’t even need to make an account for the scraper.
Public? Idk, maybe. I wouldn’t generally consider my IP to username to be public. Comment and post stuff, sort of. But even if it’s public, I still wouldn’t want Meta consuming it.
I wouldn’t generally consider my IP to username to be public.
Are they talking about your IP address or the service’s? Does ActivityPub even share the user’s IP address with other nodes in the network? That’d be crazy, so I assume that it doesn’t. Then Meta can’t find out your IP address.
If a Threads user posts an image, and Meta hosts it, and I scroll through my feed and see it, my client will hit their server for said image. And Meta can collect my IP.
Meta basically invented this shit.
Because fuck them. This is step one of their 20 step plan to do evil shit.
What if my instance says other services and instances can’t do that? Are meta then breaking the law?
Most of this is just part of Federation. When I saw this comment my client/server didn’t have to fetch it from your server. It was pushed when you posted it so I had it locally.
expired
Yes, but if you host an image, and my client prefetches it, it’s going to exposed my IP to your image server. And if you have clauses saying you’re collecting IPs…
Meta basically invented this shit. They’ll do it again. It’s what they do.
Yeah, no shit, they literally can’t federate without this data, that’s how ActivityPub works lol.
Why do you think you can see lemmy.ca votes on lemmy.world?
… why? All of this is more / less public information about you? Even if you defederate, they could crawl and get all of this info (except maybe ip).
Exactly. That fact makes the mountains of defed stuff ridiculous because it makes no difference.
Take a torch to em!
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.
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.
I don’t know what you’re getting excited about here; this is all publicly available information which Facebook could scrape at any time they wanted (federated or not), even right this very second.
Shhh, I train my AI here.
They probably already do.
Wtf. Can’t they just be defederated. Get that shit outta here.
A server admin can block any other server, including Threads.
deleted by creator
They’re literally just taking data they need to federate, like all the other instances. Eventually people around here are going to get sick of this paranoid “fuck Meta because it’s Meta” attitude because people keep posting lame misinformation like this. I know I’m getting sick of it.
It’s not just because it’s meta, it’s because they are going to scrape up all the data they can get (even if it’s just normal fediverse stuff) and pipe it into their data mining operation. They could probably easily do it without us noticing, but if we know they’re doing it… then it’s worth talking about. And reasonable for people to dislike.
They 100% could already be doing that far easier without threads. It’s not actually worth doing it though.
Whether they need it to federate or not, it’s still reasonable to not want an entity as large and powerful as Meta to consume this data. Fuck Meta because it’s Meta, which has a history of being particularly heinous with user data.
If that’s your opinion then great, that was always allowed. What I’m sick of is spinning facts and narratives to suit biases, regardless of whether or not I agree with those biases.
Wouldnt the name of your profile be more specific than your ip address so it doesnt matter if they get your ip address or not?
Also, why would they store the data? They cant show you ads
I think the policy has more to do with your server’s IP address. The language on the page is a bit vague, since they absolutely collect the IP addresses of their own users.
Removed by mod
Like tentacles of a blood sucking octopus…
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.
So they’ll grab what is needed to federate? The same stuff every instance grabs?
Ostensibly, yes. However, as a company whose business model is primarily predicated on sale of personal data and analytics, this does create something of a conflict of interest, especially because of Meta’s extensive involvement in surveillance capitalism.
Per the article, I really like Mike Macgirvin’s stance of “I’ll give you the bare minimum of data to make basic interactions work, but not one thing more.”
I mean yeah, I get the implications there, but all I’m saying is that they wouldn’t be able to federate without the info so it makes sense.
So if I read this right, no big deal as long as you don’t interact with threads stuff on the fediverse?
It’s definitely creating more of a case to defederate from it if it ever tries to federate
That’s not how I read it, but I’m not going to claim to be a fediverse expert. That post specifically says:
Provided that a Third Party User is followed by or following a Threads account, Meta will ingest these pieces of data specifically:
To me, this reads as, even if a Threads user follows you, your info gets chewed up by Meta.
In other words, if you post somewhere on the Fediverse, and some Threads user bumps into it, they can follow you, and that will send all that data to Meta. And it looks to include data well beyond the post the Threads user saw.
To me, this is a “sound the alarm” moment. If you came here to avoid Meta’s data harvesting, this sounds like you at least need to be on an instance defederated from threads, but I’m not sure even that’s enough.
Correct. Though interaction also means, a Threads user following you or replying to one of your comments or posts.
