this post was submitted on 21 Jun 2023
5 points (85.7% liked)

Lemmy

12538 readers
6 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago
MODERATORS
nutomic@lemmy.ml
5
Lemmy (and the fediverse) and GDPR: a clusterfuck waiting to happen? (lemmy.ml)
submitted 1 year ago by infamousbelgian@lemmy.ml to c/lemmy@lemmy.ml
45 comments fedilink hide all child comments
 

So, I’m kinda new to this Lemmy thingy and the fediverse. I like the fediverse from a technological standpoint. However, I think that, if we gain more and more traction, Lemmy (and by extend the entire fediverse) is a GDPR clusterfuck waiting to happen. With big and expensive repercussions…

Why? Well, according to GDPR, all personal data from EU users must remain in the EU. And personal data goes really far. Even an IP-address is personal data. An e-mail address is personal data. I don’t think there is jurisprudence regarding usernames, so that might be up for discussion.

Since the entire goal of the fediverse is “transporting” all data to all servers inside the ActivityPub/fediverse world, the data of a EU member will be transported all over the place. Resulting in a giant GDPR breach. And I have no idea who will be held responsible… The people hosting an instance? The developers of Lemmy? The developers of ActivityPub?

Large corporations are getting hefty fines for GDPR breaches. And since Lemmy is growing, Lemmy might be “in the spotlights” in the upcoming years.

I don’t like GDPR, and I’m all for the technological setup of the fediverse. However, I definitely can see a “competitor” (that is currently very large but loosing ground quickly) having a clear eye out to eliminate the competition…

What do y’all thing about this?

you are viewing a single comment's thread
view the rest of the comments
[–] klingelstreich@feddit.de 1 points 1 year ago* (last edited 1 year ago)

IANAL, but he GDPR is quite reasonable and if Lemmy did the right thing (c) it would not be a problem I think. Transferring data to a jurisdiction, like for example the US, where people do not enjoy the same level of data protection comes with risks for any eu citizen. Therefore, it is important that any new user of Lemmy/ActivityPub is educated on what's actually going on here and the consequences of posting on Lemmy for their personal data. Article 49, 1a) of the GDPR provides an exemption for the rule this posting is about if

the data subject has explicitly consented to the proposed transfer, after having been informed of the possible risks of such transfers for the data subject due to the absence of an adequacy decision and appropriate safeguards

Why can't we have that? Add a step to the signup process that explains the basics of how a decentralised community works: even if you sign up to a German Lemmy instance, Lemmy is a global community, your data may be transferred to any place in the world and that means that you won't be able to enjoy the rights and protection you may expect on a German server. Click the "accept the risks" button to continue. Go to this link if you ever change your mind to stop federation of your content and attempt to remove it from any place it has already been federated to.

Even cooler if we can somehow record the jurisdiction of instances and build mechanics that act on that information, e.g. during federation.