0
Nightmare on Lemmy Street (A Fediverse GDPR Horror Story) - Michael Altfield's Tech Blog
(tech.michaelaltfield.net)
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!
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
Not that I hold the Lemmy devs in particular high regard, but unless OP is cutting them a check every month enough to pay their full time salaries, I really don't think that he should be expecting anything just because he faced an issue that was difficult, but (a) not specific to the developers but the admins of the instance and (b) ultimately solvable.
I also think that this is not a reason to justify a whole fork or even a fully adversarial position. Yeah, tooling for moderation and instance management is lacking, but these can be built on top of the existing codebase. If my fediverser tool does that for user authentication and account management, it could also be extended for content moderation and provide granular access for staff.
Well, the bare minimum you need to do, is refuse traffic from the EU then. The devs don't want to do that, but they also don't want to implement the changes which is illegal and carried huge fines (yes, they can fine you in the US too)
The "huge fines" are proportional to the revenue of the company and there are plenty of legal steps that need to be taken before someone with a big stick gets involved.
Also, this is not an issue for the developers, but for the admins.
The fines are only proportional for big corporations. Organizations without revenue can still be fined:
https://gdpr-info.eu/art-83-gdpr/
In this case, the processing of data hinges upon the data subject’s consent, which is detailed in article 7.
Imagine a car manufacturer building cars without brakes and then saying ‘This isn’t a problem for the engineers, but for the retailers’. Of course the developers can’t be sued for this. But that’s not the point! The point is that this bug or missing feature or whatever you want to call it jeopardizes the admins upon which this whole ecosystem hinges. I can’t believe that that’s in the devs’ best interests.