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

Lemmy

12535 readers
2 users here now

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

For discussion about the lemmy.ml instance, go to [email protected].

founded 4 years ago
MODERATORS
 

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
[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

And personal data goes really far. Even an IP-address is personal data. An e-mail address is personal data.

Thankfully, Lemmy instances do not transport this kind of information about their users to other instances!

[–] [email protected] -1 points 1 year ago (1 children)

Maybe not IP addresses, but every post and comment you make is your personal data.

[–] [email protected] 3 points 1 year ago (3 children)

Public posts and comments are, well, public (and there's no expectation from users that their posts and comments would be private, considering the nature of what Lemmy is).

The only way to not transport public posts and comments to the rest of the internet (including but not limited to other Lemmy instances) would be to completely disconnect an instance from the internet 😅

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

GDPR does not distinguish between public or private data.

GDPR handles public data through propagation. If you download public data that is GDPR covered, the data you downloaded also becomes GDPR covered. You are required to follow all GDPR regulations while handling the downloaded data.

Remember, GDPR covers almost all "collected personal data". It does not matter if the data was originally public, and how/where the data was collected. It's all covered.

However, Lemmy instances may still be exempt from GDPR as they are non-commercial: https://gdpr-info.eu/recitals/no-18/

IANAL as usual.

[–] [email protected] 0 points 1 year ago (2 children)

You're confusing "private" with "personal". My data can be public, but it's still MY data and I have the right to decide what happens with it and if it should stay public. That's what the GDPR says and that's exactly what OP is referring to.

[–] [email protected] 1 points 1 year ago

You are able to edit and remove your posts on your Lemmy instance. Other Lemmy instances may or may not also reflect these changes, but your instance admin does not have any authority or responsibility to ensure that your previously public posts get deleted anywhere else in the world other than the instance they run.

That's exactly how it works everywhere, it's not a Lemmy specific thing. For example, if you write a public blog post on some public blog service, and later delete it, then it won't be the responsibility of the blog service owner to remove your post from elsewhere on the internet. It will be your own responsibility to manually request removal from other services which have copies of your post (like archvie.org etc).