this post was submitted on 09 Jun 2023
16 points (94.4% liked)
Beehaw Support
41 readers
1 users here now
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our June 2023 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
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
Few things:
If you're not comfortable with the non-compliance of GDPR on Lemmy Server, then I can suggest two things:
Yup. In order for something like the GDPR to be effective, it requires centralization to both implement and enforce. A decentralized platform is inherently incompatible with that. I don't think any attempt should be made to integrate any semblance of GDPR compliance into Lemmy's code base if it's just for compliance's sake.
Yeah GDPR compliance seems like the kind of thing that should be left down to specific instances if they want/need it, but I personally reckon that a decent chunk of the spirit behind the GDPR - namely, user privacy and the right to delete your data - is worth implementing into Lemmy at a fundamental level!
GDPR compliance is not optional for entities that interact with European citizens, you don't get to say "Oh well, that doesn't work for me". You MUST be GDPR compliant, or you WILL get fined, and the GDPR fines are no joke! Still checking and asking, but if this messages thing happens to really be a GDPR violation, every single instance admin that interacts with EU citizens (so, all of them) will be under threat of huge fines. That'd mean Lemmy would be a HUGE legal liability for instance creators, and pretty much a no-go.
The fact that this is for a feature that is also a potential huge waste of resources, as you'd keep deleted messages potentially indefinitely if the people with the accounts don't delete them, makes me feel this was not well thought out.
The reason I believe that the messages don't actually delete unless you delete your account likely have to do with moderation ability. For example, If I delete your message, everyone can't see your message but me and other moderators can see it. The reason it's put in place like that is to encourage moderation accountability. With that point of view in mind, it makes sense to have this third state of deletion.
I'm also not sure that GDPR fines would have any power if the service decides to simply not offer services in that country anymore.
That said, I recognize the issues being brought forward and it would be nice to have additional options in regards to that.
As I said, it only within the CONFINE OF THE EU JURISDICTION. Your law have no power over the American citizen and we don't have to comply with GDPR and neither does Lemmy that is hosted in USA do.
Lemmy was created to support federation of servers and the inherent problem with that is that it is incompatible with GDPR legal system, because while you can enforce GDPR on one server, you can't guarantee enforcement of it on any other servers that retain your posts or threads, because they can retain a copy of your posts thereby defeating your "right to be forgotten." So in that context, even if that one server comply with your GDPR request, is your government still going to punish that one server for something outside of their control? Lemmy, PeerTube, Mastodon, and so forth all have servers to tackle the crux of the problem in social media, The Network Effect. When you set up one server, you would notice that your one server have no content when you don't have visitors or users using that server, so you have to connect to other servers to get the contents you want and so forth, the trade off is that you can't control what goes on in that other server unless they're kind enough to give you some of that measure of control which is no guarantee.
It doesn't matter where the service is hosted, if it serves EU citizens it MUST comply with the GDPR, even if it's hosted in USA, that's why even the big companies like Google, Microsoft and all the others comply (or SAY they do, no one trusts FB on data deletion). So yes, they DO have power there.
Also, from what i understand you're assuming federation means that everything is everywhere. That is not true. From what i see from Lemmy's mechanisms (and from what my critical lack of caffeine allows me at the moment), if something is deleted on one instance it should get deleted on all as Lemmy sends the deletion request to other instances, and anything remaining from other places should be eventually deleted and flushed out of caches, that part shouldn't be an issue there. So, the instance admins would be responsible only for the data of the users in their servers, not the others. And yes, they WOULD be responsible and legally liable if this is in fact a violation (still not sure, might be OK and not even a problem as "restriction of processing" from article 18, i guess i'll continue searching tomorrow, it's 2AM here and i'm done).