I’m new to federated services here and have a question. If say Threads federates with mastodon.social and I interact with threads content through mastodon.social does Meta get my information and data or do they only get a minimal set of info like username and the instance my interaction originated from?
They would get anything the activity pub protocol gives them, which I can’t imagine is much. I’d have to look into it but I assume they’re pretty much only sharing the stuff you see.
… Ok so I looked it up (couldn’t leave it on the assumption lol).
https://activitypub.rocks/implementation-report/
Have a look at the standard here if you like. The only privacy related one I can see is the location header, but it’s optional and not implemented by most fediverse apps.
That’s not to say it will never become possible for Facebook to get more info. They will absolutely try to throw their weight around if they gain traction in the space, and could, in theory, require more info be shared for fediverse instances that want to federate with Threads. This is why it’s important that fediverse admins don’t get too chummy with the zucc.
Meta will absolutely try to appear friendly at first, perhaps offering open source development assistance, consulting or training, but it will be a farce to gain power in the space.
Got it thank you. I’m not happy about meta moving in this direction. I hope that Threads is a flop. I Ditched Facebook after the Cambridge Analytical episode and never looked back. I appreciate the info.
Embrace, Extend, and Extinguish. The term was first coined by the US DOJ, but then MS addopted it and was used internally. Basically it means that it’s a lot easier to destroy something from within than from the outside. So, you have to become “one of them” in order to set the wheels in motion.
I’m new to federated services here and have a question. If say Threads federates with mastodon.social and I interact with threads content through mastodon.social does Meta get my information and data or do they only get a minimal set of info like username and the instance my interaction originated from?
They would get anything the activity pub protocol gives them, which I can’t imagine is much. I’d have to look into it but I assume they’re pretty much only sharing the stuff you see.
… Ok so I looked it up (couldn’t leave it on the assumption lol). https://activitypub.rocks/implementation-report/ Have a look at the standard here if you like. The only privacy related one I can see is the location header, but it’s optional and not implemented by most fediverse apps.
That’s not to say it will never become possible for Facebook to get more info. They will absolutely try to throw their weight around if they gain traction in the space, and could, in theory, require more info be shared for fediverse instances that want to federate with Threads. This is why it’s important that fediverse admins don’t get too chummy with the zucc.
Meta will absolutely try to appear friendly at first, perhaps offering open source development assistance, consulting or training, but it will be a farce to gain power in the space.
Meta are ruthless in the social media space.
Got it thank you. I’m not happy about meta moving in this direction. I hope that Threads is a flop. I Ditched Facebook after the Cambridge Analytical episode and never looked back. I appreciate the info.
They get a minimal set of info, like you stated, username, content of post, post time/date. The other info stays on your instance.
That’s beside the point though, the idea is to own the fediverse, but not through hacking or data gathering. EEE is the way to go here.
I wasn’t trying to make or advocate for a point I was just wondering about the immediate/short term consequences to my personal privacy.
Also what is EEE?
Embrace, Extend, and Extinguish. The term was first coined by the US DOJ, but then MS addopted it and was used internally. Basically it means that it’s a lot easier to destroy something from within than from the outside. So, you have to become “one of them” in order to set the wheels in motion.
That’s a great description
The latter. Only your server admin has your info.