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?
Iām not an expert in GDPR and will leave the technical side to those who are, but the fact that the EU actively present at the Fediverse with among others the @EU_Commission represented at their official Mastodon instance, I would be surprised if the GDPR was suddenly weaponised against it.
GDPR was written with the intention of empowering users over corporations. The Fediverse has the same goal.
ādonāt like GDPRā? Whatās not to like? Best thing that came out of EU regulation in a long time. And as others have noted you seem to be misinformed about what it actually saysā¦
I also canāt wrap my head around ānot likingā GDPR
As a relevant example, seems like only citizens covered by GDPR will be able to request Reddit to remove all of their data from Redditās servers since comment deleting tools and scripts are being bypassed, with loads of comments and even entire profiles getting restored by Reddit admins
Can you explain where Iām misinformed? I can surely be misinformed about the workings of Lemmy. However, for GDPR you will not āwinā it with a simple TOS or something like that.
If even Google canāt make their Workplace to follow rules in such a way that Workplace can be used according to the AVG rules in the Belgian (well, Flemish) schools, Iām pretty sure that just saying āitās in the TOSā is not enoughā¦
But again, no expert so I hope that I am wrong.
deleted by creator
You are missing the point. A TOS canāt fix it. If it can, they would have done so. And for GDPR, there is no difference between schools and genpop. A citizen is a citizenā¦
deleted by creator
deleted by creator
Wellā¦ Apparently (I did some reading), the topic was about Google Workspace for Education. A solution only used by schools.
Nobody is currently ācaringā about the normal Google Workspace. So yes and no.
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!
Maybe not IP addresses, but every post and comment you make is your personal data.
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 š
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.
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.
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).
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.
Please back up this claim. Iām sure not even the best GDPR consultants out there could answer this question with confidence at this point in time.
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.
This is a completely different thing. Weāre talking about the automatic replication that happens between the different Lemmy instances, not about someone copying your comment and posting it somewhere else.
Again, I think you guys are handling OPās topic way to leasurely. The GDPR is a beast with teeth and itās going to bite your ass if you donāt take it seriously enough.
deleted by creator
Now if you want to change that, youāll have to request a GDPR deletion from every instance you posted it to.
Thatās the interesting point. Do I really have to do that or should I be able to rely on my instance owner thatās located in the EU to take care of that? Iām pretty sure none of us can answer this question. Decentralized services like the Fediverse are probably a new challange for GDPR experts.
Iām not supposing to have any answers either, but from a personal standpoint it seems rather selfish to even entertain the idea of making an instance owner do that. Itās not like these people are getting paid for a service (aside from donations, in some cases); theyāre hosting in the spirit of the fediverse. Why would I pawn legal work off to them?
You and I are not. But if a certain giant site that is currently making not theā¦ euhā¦ best decisions goes in to action with a large legal teamā¦
deleted by creator
Sure, but I in the end itās not their responsibility.
You guys sound so confident, itās not even funny. GDPR is a huge topic and everyone who already had to deal with it even marginally knows that OPās fear is absolutely plausible. The GDPR doesnāt give a shit about causing major inconviences or huge workload for platform admins. Ever heard about the GDPR nightmare letter?
This. Federation doesnāt transfer private data of the user, just their public facing profile and posts. There is no expectation of them being private.
The admin of a site, not only fedi ones but any site, can only control whatās in their reach. A user could ask as per the GDPR to have their profile and history removed, but data not in the control of the admin is not their responsibility.
Consider it from the perspective of a traditional site, if someone takes a screenshot of something you post and puts it up somewhere else the originating site has no means to control that or to remove the data from a third party location. The same issue has been fought since the dawn of the internet, people trying to erase past events that have spread far and wide. There are even proffesional services available to try and scrub such things, but in the end if all they can do is send takedown requests to another jurisdiction itās going to be an impossible task.
ITT: People that donāt undertand the difference between āpersonalā and āprivateā. My posts and comments are my personal data, even if theyāre public, 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.
Personal data according to gdpr is data that can identify you or be tied to you as an individual. Such things are e-mail addresses, phone numbers, names and so on. Posts and comments does not necessarily fulfill this. If you post your name, yes, but this comment that Iām making now would not be classified as personal data.
IMO itās pretty much the same case as email. With email you send data to some remote server which may or may not reside in the EU.
Iām not really sure what argument you can make that fediverse apps but not email break gdpr.
Or even something as simple as putting your email on a public website that may be visited by someone in the US.
You are correct. Thatās why email is a big topic in GDPR: https://gdpr.eu/email-encryption/
all personal data from EU users must remain in the EU
Create your account on a EU server, problem solved.
Lemmy (fediverse in general) doesnāt send account data away, and posts donāt qualify as personal data, when you publish something to the internet, itās public by definition.
Iām not sure this is true. Like imagine someone posts their address in a Lemmy post - Iām pretty sure that counts as PII and they have the right to request its deletion.
Like imagine someone posts their address in a Lemmy post
As you write it you can also delete it.
Itās still you willingly doing it, not the server spreading your data without your consent, this last case is where GDPR applies.
But itās a very stupid thing to do, never post your personal data in comments.
HackerNews doesnāt do this though.
GDPR Art 4.(1) āpersonal dataā means any information relating to an identified or identifiable natural person (ādata subjectā); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;
Every post and comment in Lemmy qualifies as personal data because they contain the ideas and opinions of an identifiable natural person (by their user handle). Therefore the Lemmy instances are handling personal data and must comply with the GDPR.
Ideas and opinions are NOT identifiable information, unless youāre so smart to as openly writing your personal data on a public forum (something noone should ever do, itās even bannable on reddit), your comments and posts do NOT contain and personally identifiable info, only your account does.
Personal data is not identifiable information. Personal data is information about an identifiable person. The identifiable information is your username (āonline identifierā)
There is no way someone can link your username to who you are in person, unless itās you who write it out.
Laws donāt protect people from themselves.
An individualās social media āhandleā or username, which may seem anonymous or nonsensical, is still sufficient to identify them as it uniquely identifies that individual
Neil Brown did quite a good write-up on the legal standing of the Fediverse late last year: https://decoded.legal/blog/2022/11/notes-on-operating-fediverse-services-mastodon-pleroma-etc-from-an-english-law-point-of-view
Thereās a section part way down about GDPR, but the answer is āit dependsā
Thanks! The info actually makes sense. Also, do note that every EU country has their own specific implementation of the GDPR law with very small differences. So this is written according to the UK implementation, but the BE implementation might be just a bit different.
All complicated stuffā¦
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.
It doesnāt work like that, think of your instance being a proxy to the fediverse
Is it? I read somewhere that data effectively gets ācopiedā to the different instances? But that might be wrong info :p
Then it should be the responsibility of the EU people to avoid joining the fediverse. I do not see a practical way to align with GDPR. The effort is non-trivial and the rewards are extremely minimal.
From your perspective, what should be the way out?
Then it should be the responsibility of the EU people to avoid joining the fediverse.
The instances are providing their services in the EU, so itās legally up to them to comply with the GDPR.
From your perspective, what should be the way out?
Honestly, no idea. Iām not even sure if Lemmy in its current shape violates the GDPR in the first place, but if I were the admin of a large feddit instance in the EU I would make sure to get advise from a GDPR consultant.
But when a lemmy.world user subscribes to a feddit.de community, the entire community will be copied to the lemmy.world server, or am I wrong?
You are indeed wrong. The email and IP addresses and passwords for example donāt get copied. Iām not well versed enough about how it works to go into more detail.
You are indeed wrong. The email and IP addresses and passwords for example donāt get copied.
I never said that IP addresses and passwords were getting copied.
The thing that no one seems to understand here is that all my posts, comments and votes and everything are my personal data. 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.
If what you say is true, thenā¦ Email is illegal in the EU. EMAIL.
Yeah, no, GDPR, although well intentioned against large corporate entities that have all the power in centralized system, is a relic in the context of federated technology. It is both completely unenforceable, and also not really relevant.
If what you say is true, thenā¦ Email is illegal in the EU. EMAIL.
No, but there are actually certain things you need to take into consideration when it comes to GDPR and email.
What the GDPR says:
Data erasure is a large part of the GDPR. It is one of the six data protection principles: Article 5(e) states that personal data can be stored for āno longer than is necessary for the purposes for which the personal data are processed.ā Data erasure is also one of the personal rights protected by the GDPR in Article 17, the famous āright to be forgotten.ā āThe data subject shall have the right to obtain from the controller the erasure of personal data concerning him or her without undue delay.ā There are some exceptions to this latter requirement, such as the public interest. But generally speaking, you have an obligation to erase personal data you no longer need.
What it means for email: Many of us never delete emails. There are plenty of good reasons: We may need to refer to them someday as a record of our activities or even for possible litigation. But the more data you keep, the greater your liability if thereās a data breach. Moreover, the erasure of unneeded personal data is now required under European law. Because of the GDPR, you should periodically review your organizationās email retention policy with the goal of reducing the amount of data your employees store in their mailboxes. The regulation requires you to be able to show that you have a policy in place that balances your legitimate business interests against your data protection obligations under the GDPR.
https://gdpr.eu/email-encryption/
I still donāt see a reason why Lemmy shouldnāt be affected by the GDPR and why itās probably not compliant in its current state.
The last paragraph you quoted is in reference to individual responsability and how they access the data. Itās equivalent to saying ādonāt look at at this Fediverse post: you are GDPR compliant!ā. This only helps you in litigation. We both know that says nothing of where the data can exist. And this is true for any federated system, including email.
Itās also completely asinine. Suddenly we need to burn snail mail after reading it? Why receive any mail at all if everything is a giant piece of liability? Thereās a social contract in communication: a certain assumption that if you give someone a piece of informtion, you are doing just that: giving, not lending. āLending informationā upsets the social structure. GDPR has to be tempered in reality, and this starts even before the fediverse.
Like I said, GDPR is imperfect. It was written in the context of and solves a problem created by centralized institutions and large beaurocracies. It is also completely unenforceable in a decentralized system. It hardly seems relevant anyway.
Realisticalpy speaking, those tempered interpretations are probably already existant, and there is already enough precedent for this to be a nothing burger.
This whole thread is full of interpretations and gut feelings. Literally no one here backs up their claims with any kind of evidence.
sure, but no personal data like email/ IP
I think you, being an admin of a huge Lemmy instance, would be well advised to educate yourself on the difference between āpublicā and āpersonalā when it comes to GDPR compliance. All the data I create here is my personal data, no matter if itās my IP, my mail address, posts, comments or votes and the GDPR says that itās my right to decide what happens with my data and if it should stay public. The fact that I post something publicly doesnāt make my data non-personal.
deleted by creator
Ok, so I did some checking regarding the location and stuff, since Iām clearly not informed enough about this. However, my point still stands (I think).
Copy pasted from Twilio. I guess they are better aware than I am about the rulesā¦
The general principle for transfers is outlined in Article 44, which can be summed up as saying, if you transfer EU personal data out of the EU, make sure that this data still enjoys the same level of protection it gets under GDPR. In other words, the entity or company that you pass the data to outside the EU must be under a legally binding obligation to follow GDPR data protection principles or the equivalent. (Unlike an outright prohibition on extraterritorial data transfers, this actually makes sense. No point if having rules if those rules get tossed out the window just by moving the data out of the EU.)and also:
This legally binding obligation can be achieved in multiple ways. Here is a sampling: 1. The entity to whom you pass the data to happens to be in a country that has data protection laws that are just as strong as GDPR (as determined by the EU Commission). 2. The entity to whom you pass the data to agrees by legally binding contract to follow GDPR principles of data protection. 3. The company has enacted Binding Corporate Rules. 4. There is some regulatory-approved code of conduct to which the entity subscribes.So, if someone opens up an instance in, letās say, Ethiopia or the US, it is not compliant, afaik.
However, question remains about the proxy thingy of the fediverse. Is data copied/stored on other instances OR does it remain on the instance that I subscribed to. And what if that instance is located in a ānon-GDPR-compliant-environmentā?
I donāt think a TOS will hold up. GDPR (and the implementation per country) is a law. You canāt bypass a law with a TOS, I think.
However, Iām definitely not a GDPR expertā¦
