160
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Jun 2023
160 points (100.0% liked)
Technology
37742 readers
494 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
I think an option for full data deletion would be nice for those who want it, otherwise people should also expect others recording their data, which can be published later on.
Parts of it may actually be required under EU law. GDPR requires that anyone holding data on EU citizens comply with certain things, including a request to delete certain kinds of data. The EU has shown themselves willing to go after sizeable corporations for violations; most Lemmy instance operators are much smaller. This should probably be addressed before people find themselves on the wrong end of lawsuits.
Thing is, Lemmy is easily compliant with the EU's laws on this, because the laws state that the EU citizen merely needs to request the data be deleted. It says nothing about them having direct access to the lever to do it.
A basic Python script can be used purge the database after a written request and everything's kosher.
I don't understand why posts are held in reserve, rather than outright deleted. That's a design decision that doesn't totally make sense to me. I can see holding on to it for a period of time - 24 hours, 7 days, 30 days, what have you - so that users can undelete things, but just hiding it from end users and calling it deleted seems pointless to me.
It's not like anyone is trying to sell it to 3rd parties for model training. And while I could see a use case in academic research, the delete button seems like an implied revocation of a license to show or distribute the content, at least in the absence of a proper ToS.
And it just makes more noise for admins and mods.
I don't think GDPR necessarily applies here, but I am not a lawyer. Quoting https://gdpr.eu/companies-outside-of-europe/:
I'm not sure just what the definition of an organization is, so perhaps any server hosted within the EU is covered by the GDPR, but for servers outside of the EU that don't have ads (which seems like all servers currently), I don't think this would count. The example on the linked site about "goods and services" includes stuff like looking for ads tailored at European countries, so I suspect that simply serving traffic from Europe isn't enough.
The website also mentions the GDPR applies to "professional or commercial activity". There's also apparently an exception for under 250 employees. I don't even know how that works when something is entirely managed by volunteers like this currently is.
At any rate, I suspect we're a long way off from having to worry about the GDPR.
The GDPR itself doesn't use the term organisation, it refers to data controllers and data processors.
As someone from within the EU working in data the fediverse is absolutely not a long way off having to consider this, GDPR impacts even the smallest businesses or voluntary groups - it's just how we handle data.
To make it easier to grasp GDPR is about your rights over your data, those don't change depending on who is processing it, nor does the processors obligation, however what would be considered appropriate safeguards would scale with the size and intent of your organisation - it would be silly for my local shop to have a data protection officer.
I suppose the question would become who is the controller, is it the person who provides the software or the person who provides the servers? Typically it's the servers.
Gdpr applies to servers within the EU, or for servers with EU clients. You can demand that they delete and stop transmitting data.
But you accept to transmit data all over the world, in the end that data could end up somewhere outside of the EU without any direct EU customers. Then all bounds are gone.
GDPR likely doesn't apply to public facing forums in the way you're thinking, if you post actual personal data (which has a strict definition) yes it's murkier, but in general just posting on a public facing forum is extremely unlikely to qualify under right to be forgotten under GDPR.
Notably, GDPR is extremely unclear about this specific circumstance, and will likely fall to practicality. The user can make requests for their data to be deleted, those should in general be followed no matter who's server it's on, but they have to be given to each server by the user. Following the deletion requests is generally advisable, but again, it's highly unlikely GDPR applies here. Feel free to get a GDPR lawyer to actually weigh in though.
Part of it will depend on what data you're holding, and part will depend on who's running the instance. A lot of people won't be covered, but I'd wager there's some here and there who need to consider it.