How does this instance feel about this growing pact against federating with Meta?
How does this instance feel about this growing pact against federating with Meta?
Meta/Instagram launched a new product called Threads today (working title project92). It adds a new interface for creating text posts and replying to them, using your Instagram account. Of note, Meta has stated that Threads plans to support ActivityPub in the future, and allow federation with ActivityPub services. If you actually look at your Threads profile page in the app your username has a threads.net tag next to it - presumably to support future federation.
Per the link, a number of fediverse communities are pledging to block any Meta-directed instances that should exist in the future. Thus instance content would not be federated to Meta instances, and Meta users would not be able to interact with instance content.
I'm curious what the opinions on this here are. I personally feel like Meta has shown time and time again that they are not very good citizens of the Internet; beyond concerns of an Eternal September triggered by federated Instagram, I worry that bringing their massive userbase to the fediverse would allow them to influence it to negative effect.
I also understand how that could be seen to go against the point of federated social media in the first place, and I'm eager to hear more opinions. What do you think?
You're viewing a single thread.
Meta has repeatedly introduced features intended to scrape larger amounts of data about our lives and tie it all into one big profile that they can sell. This area of the internet feels like one of the few remaining areas that they haven't reached, and I'd bet everything I have that's why they're introducing this. I couldn't be more strongly against allowing them a way to link my data here with the data they have from my usage of their existing products. While I understand the idea of open federation to allow disparate communities to interact, one of the lines I'll draw is letting a massive corporation in like that.
They'll still be able to scrape the fediverse and all instances without threads federating with them. Defederating doesn't stop their access to your PUBLIC data on the fediverse.
Anyone can access the public data, but that is not a good excuse to invite them in through the front door. Defederating, at the very least, sends the message that they are not welcome to participate here.
And not being welcomed is going to stop them?
The guaranteed way to fail is to not even try to succeed.
I mean, we have nothing more to lose if they are hypothetically going to succeed. What does it cost us to just try? Why are so many people against even trying, despite it requiring absolutlely zero effort from most of us? Why rush to submit to bad things before they happen?
I'm curious, are there policies for usage of data on a service like this? If you federate Meta (or any instance, or this instance), is that granting them the right to use your data as they wish? Assuming the answer is yes, could the Fediverse at large implement a broad, let's call it "Terms & Conditions", that must be acknowledged upon federation, regarding how the data is used? Or, if the answer is no, what are the limitations to how data in the Fediverse is used?
Also, how useful is my data to them anyway, if they can't target me with ads? Certainly there are uses, but isn't the primary end-game just selling me something? If I'm on an independent instance, I'm not sure how much I care about them having access to my data.
Edit: Mastodon founder Eugen touches on some these questions here. This is specific to Mastodon, I have no idea how much of this carries over for Lemmy.
Will Meta get my data or be able to track me? A server you are not signed up with and logged into cannot get your private data or track you across the web. What it can get are your public profile and public posts, which are publicly accessible.