this post was submitted on 19 Jun 2023
240 points (100.0% liked)

Technology

37739 readers
500 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] asjmcguire@kbin.social 22 points 1 year ago* (last edited 1 year ago) (32 children)

I'm personally happy to take a wait and see approach - because the whole point is that WE have the power. Meta HAVE to play by the rules, because if they don't they get defederated, and it's going to be very difficult for them to convince people to federate with them again after that. If lots of instances start defederating them, then their users are going to start complaining to them that they don't understand why they can talk to some people, but not other people. We have the power here folks.

EDIT: To add - the Fediverse is supposed to be an inclusive place.....

[–] polygon@kbin.social 23 points 1 year ago* (last edited 1 year ago) (17 children)

Well, the big issue here is that we sort of don't have the power you think we do.

What I mean is, say you have 10 servers. 7 are Lemmy, 3 are kbin. Great, each admin has control over those servers. Then you have Meta. They'll run 1 huge server. When the 10 other servers enable Federation, Meta now has 10 servers of content that isn't even on their own platform that they can sell. Your data will literally exist on the Meta server because your data is not contained within your instance/platform once it's Federated. Meta can then harvest the entire Fediverse for data like this. It's like an absolute wet dream for them. They don't even have to coax people to use their own platform!

Meta must be defederated the second they so much as dip a toe into the Fediverse or everything you've ever done, or do, on any ActivityHub platform will be scooped up and sold.

Edit: And it's even worse because all it takes is 1 server to Federate with Meta. If server A is Federated with your sever B, Meta can sill pull your data from server A they Federated with, even if your local server B has Defederated with Meta. This is a huge problem.

[–] feduser934@vlemmy.net 8 points 1 year ago* (last edited 1 year ago) (6 children)

I'm confused about what kind of data you want to protect. If you mean your posts and comments, they are already publicly availible on the Internet. Meta doesn't need to make a activitypub app that gets federated with Lemmy to aggregate and sell this data.

Is there an other kind of data that is visible only to server administrators?

[–] 6fn@kbin.social 2 points 1 year ago* (last edited 1 year ago)

Someone correct me if I'm getting details wrong, but from reading this post it appears as if fediverse admins are provided both the username and email accounts registered by those users that have visited their instances.

If that's true, one problematic scenario I can imagine is when someone has registered on the fediverse with a pseudonym, but has an e-mail address they also use on their real-life Facebook profile. Visiting a Facebook-run ActivityPub instance while logged in would give Facebook enough data to link both the pseudonymous account (with past and future post history), and the real-life Facebook profile.

So, even if you're not signed up for Facebook's version of ActivityPub, engaging with it could still be giving Facebook a source of ongoing data for building personal profiles and targeted advertisement that people would not provide on their own.

load more comments (5 replies)
load more comments (15 replies)
load more comments (29 replies)