I’m kinda torn here.
On the one hand, this is Meta we’re talking about. Fuck’em.
On the other, this is all public info on insecure social media. It can all be scraped by anyone who wants to anyway.
Threads' New Terms and Conditions Affects the Fediverse
Submitted 1 year ago by throws_lemy@lemmy.nz to privacyguides@lemmy.one
https://wedistribute.org/2023/08/threads-new-terms-affects-the-fediverse/
Comments
Steve@communick.news 1 year ago
AdminWorker@lemmy.ca 1 year ago
Can activity pub change it’s terms to say that all crawlers that use this must be gnu open sources and all information crawled must be open to the public on gnu open sources software?
Nerd02@lemmy.basedcount.com 1 year ago
Isn’t ActivityPub just an application protocol? To my knowledge there’s no ActivityPub inc. licensing the usage of the protocol or anything like that. A web protocol is just a series of guidelines everyone has agreed on following, you can’t attach terms and conditions to it.
duncesplayed@lemmy.one 1 year ago
Indeed. Licensing usage of something is antithetical to free software culture anyway. It would violate the Free Software Foundation’s Freedom Zero, that you should never have to accept a licence to use something. (This is why free software cannot ever, by definition, have a EULA, for instance)
Laitinlok@discuss.tchncs.de 1 year ago
The thing they could do is block the servers of Meta or route to tor for anything sent to meta.
squid@feddit.uk 1 year ago
This is a good shout
scottmeme@sh.itjust.works 1 year ago
Everyone needs to defend from them
Whirlybird@aussie.zone 1 year ago
Why, because they otherwise would get the same data that every other instance already gets?
This is a big nothingsauce. “Meta gets access to public fediverse data when meta joins fediverse” should be the title.
Mane25@feddit.uk 1 year ago
None of that is particularly the thing that worries me - Meta could be crawling Lemmy right now and getting all that information even if they weren’t planning on supporting federation, but it’s on the public web intentionally to be read, so it’s just like anyone else reading it. The only piece of information I’m surprised would get shared is IP address, and without knowing the technical reasons I’m wondering how/why they would get this and if it’s something Lemmy could fix in software.
The main thing that worries me is still if the toxic culture of Meta’s social networks floods into our communities.
cedarmesa@lemmy.world 1 year ago
Few questions for the techy bros and gals.
1 Can threads collect this info on me if I block their instance? 2 Does this only happen if and when they federate? 3 Are they already federated? 4 When will they federate? 5 What steps should I take to protect my information?
FaceDeer@kbin.social 1 year ago
That information is already public knowledge (aside from your IP address, I assume the Threads policy is actually talking about the instance's IP address). I can collect all of that info about you right now myself, without even running my own instance, because kbin exposes that data. Every other instance that your posts touch gets that info too.
If the Threads instance was defederated, sure, they wouldn't see it through that particular view. But they could be quietly running any number of other instances out there already just for the purpose of harvesting that info. Or they could be using a webcrawler or an API to get the info from some other third-party instance.
I think ultimately people need to accept that when they post something publicly - post,s comments, profiles, etc - then by the very nature of it being "public" everyone can see it. You can't simultaneously "protect" and "publish" this information at the same time. It's the DRM paradox, but even harder to resolve than the usual. The only way you can "protect" this information is to not publish it in the first place - ie, don't have a profile on the Fediverse and don't post comments on it. Because the Fediverse is designed to spread that information around.
Kaldo@kbin.social 1 year ago
Please read the article. The data in question, besides the IP that I don't see how they can store since it's coming from your instance and not the user directly, is the bare minimum that's required for AP to even work, and it is the same data that every federated instance is already storing and propagating.
Facebook is a shit company but the privacy of this data is not one of the issues with it. As has been said before already, all of this is already very public, very easy to scrape and it is impossible to prevent it, if you want to keep your profile picture, username and comments private then dont upload them to a federated social network... or well, any social or network at all.
jet@hackertalks.com 1 year ago
If somebody else’s federated with them and you comment on a discussion hosted by them, then meta will have your post information
nixfreak@sopuli.xyz 1 year ago
You have to block all thread domains and instances.
CookieJarObserver@sh.itjust.works 1 year ago
Everyone that hasn’t defederated them by now should now.
hellfire103@sopuli.xyz 1 year ago
Would it be possible to blacklist Threads, but also whitelist specific accounts? I don’t want any more to do with Meta than I already do, but I’d also like some way of sending questions into The Last Leg.
bamboo@lemmy.blahaj.zone 1 year ago
How does Meta/Facebook get access to IP Address information of the user. Is that public in ActivityPub spec?
jet@hackertalks.com 1 year ago
TLDR - anything the fetty verse sends via activity pub will be recorded by meta.