this post was submitted on 04 Jul 2023
3340 points (96.2% liked)
You Should Know
33006 readers
49 users here now
YSK - for all the things that can make your life easier!
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must begin with YSK.
All posts must begin with YSK. If you're a Mastodon user, then include YSK after @youshouldknow. This is a community to share tips and tricks that will help you improve your life.
Rule 2- Your post body text must include the reason "Why" YSK:
**In your post's text body, you must include the reason "Why" YSK: It’s helpful for readability, and informs readers about the importance of the content.
**
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Posts and comments which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding non-YSK posts.
Provided it is about the community itself, you may post non-YSK posts using the [META] tag on your post title.
Rule 7- You can't harass or disturb other members.
If you harass or discriminate against any individual member, you will be removed.
If you are a member, sympathizer or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people and you were provably vocal about your hate, then you will be banned on sight.
For further explanation, clarification and feedback about this rule, you may follow this link.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- The majority of bots aren't allowed to participate here.
Unless included in our Whitelist for Bots, your bot will not be allowed to participate in this community. To have your bot whitelisted, please contact the moderators for a short review.
Partnered Communities:
You can view our partnered communities list by following this link. To partner with our community and be included, you are free to message the moderators or comment on a pinned post.
Community Moderation
For inquiry on becoming a moderator of this community, you may comment on the pinned post of the time, or simply shoot a message to the current moderators.
Credits
Our icon(masterpiece) was made by @clen15!
founded 1 year ago
MODERATORS
Good find, albeit a bit horrifying.
I wonder what the GDPR implications of this is. As far as I understand, even free, privately run services are required to abide by GDPR and offer data insight and deletion. They're also required to state clearly what happens to user data.
Edit: Apparently people have varying takes and feelings on what the GDPR does and does not say, so I urge you to please read the summary of GDPR data privacy here: https://gdpr.eu/data-privacy/ as well as the summary of what constitutes personal data here: https://gdpr.eu/eu-gdpr-personal-data/ It's easier to have a good and fruitful discussion if we talk about what the GDPR actually says.
I've been wondering exactly this, Lemmy will have to be shut down in the EU if it doesn't comply with GDPR, and considering that means each individual instance and the individual/group/company running it...
I just don't see how this is ever going to be secure enough to fully comply with GDPR. Not when huge security holes like this exist, where anybody with a tiny bit of knowledge and a few hours can access so much data on people anywhere...
According to the GDPR an "organization" has to specify exactly who processes the user's data (i.e. every instance in a federation — past and present), and everyone that processes that data must make it easy to make data/deletion requests, to that's hopefully baked into Lemmy from the get-go because otherwise someone is going to find themselves in the middle of a GDPR nightmare sooner rather than later. It's not enough to say in the privacy policy that "user data spreads to federated instances" or something to that effect.
And given that usernames are connected to the votes, I'm pretty sure that it does not comply with the GDPR to just say that it "will place this interaction in the user's outbox and immediately deliver it on the user’s behalf to all".
Edit: Added link.
I don't think email is a good example because you're in complete control of who you send an email to. However, I'm not in control of who Lemmy sends my voting data to (because I don't control who a given instance is federated with), but GDPR grants me the right to know that.
Still not a good example because I'm still in control of what I choose to send and whether or not I choose to send it at all. I can't choose whether or not Lemmy broadcasts my username in conjunction with my votes to whoever may be listening, but I can choose not to send an email to a mailing list stating who I am and how I vote on Lemmy posts.
Organizations handling EU citizens' data are required to abide by the GDPR and I can assure you that Gmail and others do that, they were among the first scrutinized when the GDPR went into effect. Just because I can send any data via email, doesn't mean that email providers can do whatever they want with the data. If an email provider processes the contents of your email in order to do targeted advertising, then they have to very clearly state that in their privacy policy.
This isn't specifically aimed at you, @cwagner@lemmy.cwagner.me, but more of a general observation. Lots of people in this thread appear to be unfamiliar with the GDPR and how it works, and that's completely fair — especially if you're not from Europa and/or haven't worked with it. I just wish they would actually check how it works instead of making assumptions. This is a good start: https://gdpr.eu/data-privacy/
It absolutely does. When sending an email, you fill in the recipient and decide where your data goes, but when you press 'upvote' on Lemmy, you don't have a say in who that information is broadcast to — especially not in its current form. And it's on whoever runs the Lemmy server to comply with the GDPR and make data processors known. It really doesn't matter how similar you think it is to email, the GDPR treats it differently and that's the reality you have to accept.
Your argument could easily be extended to every piece of information floating across the internet. No one is forcing anyone to upload an image to Facebook, but Meta is still responsible for documenting who handles the image and for what purposes, they can't just say, "you uploaded it, we let 3rd parties have their way with it".
And I've also worked with the GDPR, both as a developer implementing systems to accommodate requests for data insight and erasure, and implementing controls to make sure data was being handled correctly and e.g. not stored for longer than allowed, and I've worked with it from a security perspective in order to protect the personal data of about a couple of million people, and finally I've worked with it in management to implement safe and GDPR compliant data handling strategies in a couple of companies.
I am interested in discussion but I prefer to discuss things based on facts rather than feelings.
Email isn't exempt from the GDPR. If an email provider is doing anything with your email except for delivering it to the intended recipient, then you have a right to know under the GDPR. Plenty of hefty fines have been handed out over failing to sufficiently inform about such things: https://www.enforcementtracker.com/ (look for e.g. art. 12 violations). Even something as simple as SMTP logs contain PII according to the GDPR and should be handled as such.
You voluntarily sending an email, with whatever content you decide to put there, to a recipient of your choosing, is in absolutely no way the same as clicking a vote button and involuntarily having your vote and username broadcast to whoever cares to listen without your prior knowledge and consent. Yes, emails travel through a bunch of MTAs underway — that's a prerequisite for email to work. And no, broadcasting Lemmy votes along with usernames is in no way a prerequisite for voting to work.
Yes, and that's not the issue as I've been saying the entire time. The issue is that you have a right to know where it's broadcast — both in the past and in the present. That's what I've been saying the entire time. And the privacy policy needs to specify exactly what data is sent and where to. The privacy policy you cited did neither, it just stated that it was sent out.
You can easily check which instances your server is federated with in the footer of your server. If any of those external servers have subscriptions to the community you're posting in, they will receive an update, so it's safe to assume it's being sent to all of them.
Problem is that it's not historical. If a server was defederated yesterday, it doesn't appear in that list. And again, GDPR takes this stuff seriously, and "look at the bottom" is not sufficient. It needs to specify what data goes where.
I wonder how deletion of user data is supposed to work in that regard. Since everything is synced to all federated instances, I guess one would have to file a request for deletion with every instance separately (?)
I have extensive experience with complying with GDPR and I feel like they wouldn't care that it is decentralized. They'd go after Lemmy as a whole and anyone involved. Having to request your data wiped from each instance is not something they are going to accept.