Yesterday, as part of the discussions related to Lemmy current inability to delete all user content I wrote a proposal: if enough people stepped up to help with funding, I'd take my work on my Fediverser project (which already has an admin web tool that "knows" how to interface with Lemmy) to solve all the GDPR-specific issues that we were raised by @maltfield@monero.town
The amount asked is, quite frankly, symbolic. I offered to work 10h/week on it if at least 20 people showed up to contribute via Github (which would be $4/month) or to signup to my instance (which access is given via a $29/year subscription). In other words, I'm saying "Give me $80/month and I will work 40 hours per month on this thing which so many of you are saying is critical to the project."
So now that we have passed 24 hours, 58 upvotes and a handful of "that's great!" responses, let me tell you how that translated into actual supporters:
- Zero sponsors on Github
- Zero signups on Communick.
Don't take this as me demanding anything. I'm writing this just to illustrate the following:
-
The Tragedy of the commons is real. I can bet that at least 30% of the 60+ thousand users on Lemmy are proud owners of a pricey iPhone, and most of these are okay with paying for an app to use on their pricey iPhones, but almost none of them will even consider throwing a few bucks per year on the way of an open source developer.
-
The Outrage Mill is not a "capitalist" or even "corporate" phenomenon. People were piling on the devs yesterday for completely ignoring "such a crucial piece of functionality", but no one actually stepped up to offer (or gather) the resources needed to have this problem solved. It's almost as if people were getting more out of the discussion about the problem than working through a solution.
-
"Skin In The Game" is a powerful filter. No matter how much people will tell you that something is important to them, the true test is seeing how many are willing to pay the asking price. If not people are not willing to pay $2 per hour of work, then I can assume that this is not really important.
Can you show where the GDPR excludes public information? Because if it doesn't and can uniquely identify a person, then it's still subject to this regulation.
Let's say you go to a public forum and asks "please remove my PII". To comply, they don't need to remove your comments and posts, they just need to remove your username. Granted, the website owner might have the policy of deleting all the content, but you'll have a hard time with the legal system to argue that they are not complying with the GDPR if they delete only the thing that really just identifies you uniquely.
But what if some of my comments include information that can uniquely identify me?
That can be something like "message me on Matrix at ..."
It's not "uniquely identifiable". What if someone else writes your information as their own?
Again, I feel like there is a lot of conjecturing when the best thing to do would be to get an actual lawyer to make a report indicating what about Lemmy today is in violation of the GDPR. For all the crying around it, I'd bet that the issues are not insurmountable, and I think that we should stick with common sense: those that care about actual privacy should not be using a social media platform anyway, and they should always be treating anything they put online as something that is never going to be deleted and available for any sufficiently motivated actor.