this post was submitted on 06 Mar 2024
303 points (88.9% liked)
Fediverse
28724 readers
133 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
how are you supposed to do gdpr compliance on a federated system though?
You are responsible for data collected by your own instance. If a deletion request comes through, you are responsible for deleting it from your account, and forwarding the deletion request and responses to other instance you federate with. You are in the clear as long as you don't keep data you legally can't, and have sufficiently informed other instances of your obligations.
No, if you collected the data and shared it with others, simply informing the others is not enough. This is why the platform needs tools for admins to comply.
A proper method, that allows the users to nume their account could already be enough.
What I mean by informing others is that you have to explicitly forward the deletion request. Not much else you can do I think.
I get that, but this is where it gets tricky. As "there is nothing we can do" was the number one reason used under the law predating the GDPR. So in the GDPR there is a stipulation that you stay responsible or share responsibility with the other party If you share the data. Because large companies used this to send data through clearing houses allowing them to hash their hands.
GDPR is really the cranky brother of its predecessors, because there was so much fuckery going on.
And while I doubt Admins will be a prime target for privacy watchdogs, it is good that they also have to think about the privacy of their users. Since privacy is a basic human right.
Oh, that's actually neat. But at the same time, that means every instance owner is responsible for the whole of the Fediverse.
I can imagine that would mean non-compliant instances will get defederated at some point? Or ActivityPub will get some compliance features? It's not like the EU is unaware of the Fediverse, they are the main monetary supporters behind Lemmy.
I have no clue how jurisprudence would turn out. But keep in mind, this is not about the posts people make. The framework just needs to collect/store as little information as possible that can be considered PII. And it should have a way to remove it.
If Deleting your account results in the PII actually being removed (username, ip address, other profile info, whatever data is stored under the hood) and these removals actually get federated.. there should not be an issue.
Then admins maybe have to do something if people start posting PII as messages, but that would probably be doxing and up for removal anyway.
So mainly the issus boil down to:
The issue I see is that if my instance is on the hook for the fediverse at large, and I operate on an allowlist basis, malicious actors can scrape PII and ignore the GDPR, and that would make me the one on the hook for that, isn't that right?
There is plenty of jurisprudence and clarity needed, so..... maybe. Hence the importance for the framework itself to be as GDPR compliant as possible and not store PII if not nessecary and remove it once no longer nessecary. (Storing someone's IP for login, and post validation, bans etc should be limited to the period that makes sense, not infinitely.)
And in your example, the 'malicious' part of the 3rd party probably makes it different. Maybe then it is a dataleak.
You can't and this is a shit article...the GDPR doesn't apply to instance outside of the EU....
https://www.dickinson-wright.com/news-alerts/what-usbased-companies-need-to-know#:~:text=The%20GDPR%20even%20applies%20if,language%20of%20an%20EU%20country%2C
Literally people using the GDPR like it's some gotcha thing for admins. If nothing is sold or offered to be sold and their is no financial gain it's not going to apply. On top of that good luck suing a FOSS dev.
Edit: that downvote button does jack shit on Lemmy people. If you think I'm wrong why not prove that I'm wrong...and why a bunch of law firms are wrong as well.
It absolutely does, if the company processes data of EU residents. The US enforces GDPR themselves, as they have signed an agreement to do so. To be clear, this means that according to US law, if you are a US web host, you can abuse US customer data and the FBI will not come after you, but if you do so with EU customer data, US authorities will come after you on behalf of the EU.
Yeah it does, as soon as you are providing a service, if you have a user from the EU that's not you, it applies. And while GDPR fines are defined in a revenue percentage, there is a minimum of "up to 10 million EUR" for a violation.
Nobody is getting sued. EU data protection agencies don't "sue" people and companies. They fine them. The difference is that a lawsuit is a process where at the end you might need to pay money, but you mostly settle. A GDPR fine looks like you get a letter saying you need to pay an amount, if you want to appeal, you can do so after paying.
And it's not the devs that will be getting these fines, it's instance admins.
And this is why misskey is a mastodon instance that just blocked access if the person is from the EU, it's too much to ask for devs in a single digit that survive by donations or their own pocket money, this is a hobby for them.
Yeah, their main income is from a Dutch based EU fund to help Foss projects. So maybe, just maybe they can then fix issues in following dutch/eu law.
Did they defederate from all instances allowing access to EU citizens? If not, they are still liable, as they are scraping EU citizen's data for federation. Even usernames are personal data according to the GDPR.
No it does not, the instances are free, no one is making money off user data or selling anything to the user. It does not apply period.
No it does not, if you do not sell anything to anyone or offer any services or make any money it doesn't apply. Stop repeating bullshit.
Good luck fining a host admin, of a foss instance. I don't know why you think that any admins of instances will be getting fined if they're not selling anything. You need to read up on the GDPR.
Again, no they will not.
Why are you trying to be an authority on GDPR without even reading about what it is?
GDPR applies to all personal data of people currently in the EU. If you have a service that uses data from a person in the EU, you need to comply with it. It's not some "gotcha" law which goes in effect once you make money.
What personal data is a Lemmy instance holding onto?
I'm pointing out how much bullshit is being spread in this damn thread by people who don't understand the law. You're the same damn users who get pissy with forums and demand action be taken using a law you don't understand.
You are the one who doesn't understand the law.
Says the guy who's literally arguing with what lawyers in the USA say about the GDPR...good one.
Show me a lawyer that says "if you are processing data of EU citizens you can't get fined in the US". You don't know anything about GDPR. It's not some toothless law that only works in Europe.
What part of personal data do you not understand? Lemmy instances are no processing any personal data
And the link I provided has already stated this, but here it is again.
https://www.dickinson-wright.com/news-alerts/what-usbased-companies-need-to-know#:~:text=The%20GDPR%20even%20applies%20if,language%20of%20an%20EU%20country%2C
As per official EU communication:
Lemmy instances are entities that offer free services and are arguably monitoring the behaviour of individuals in the EU through federation. From the perspective of the GDPR, there is no difference between Facebook and a Lemmy instance regarding what they can or cannot do, or whether they get fined for something.
You need to read up on the GDPR yourself.
What personal data is being processed by a Lemmy instance, what are they processing that's being sold in the EU? The GDPR does not apply here, stop trying to wiggle it into something it's not.
Usernames at the very least, as online identifiers.
And they don't need to be sold, just retained. GDPR applies even if there is no payment anywhere, even to non-commercial entities.
Usernames are not PII...the GDPR only applies if someone is making money from the service. It does not mean just because your site is free but hosts ads or sells user data it's exempt. Lemmy instances do none of this.
What do you think an online identifier is then? And why would the GDPR only apply if there is money made? It specifically says in multiple places free services also count.
https://www.ibm.com/topics/pii#:~:text=Personally%20identifiable%20information%20(PII)%20is,email%20address%20or%20phone%20number.
Usernames are not and never have been considered pii
The GDPR states it clearly that the company/entity has to be collecting pii or selling something to the person. Lemmy does neither of these.
How is IBM authoritative on this subject? And even so, this article doesn't say that usernames are not PII, it even indirectly says it is indirect PII.
Here's another random company's page saying usernames are PII: https://www.keepersecurity.com/blog/2023/06/14/what-is-personally-identifiable-information-pii/
The GDPR says it clearly and explicitly that:
Usernames that are used in an internal network are, because they're linked to pii, a public username is not pii.
And where did you read that? If anything, public usernames are easier to correlate to form identities.
Use this for starters https://www.eff.org/deeplinks/2022/12/user-generated-content-and-fediverse-legal-primer
Nothing in there about the gdpr... literally 0, because it's not part of hosting a forum that doesn't host private user data or collect non essential cookies.