96
Nightmare on Lemmy Street (A Fediverse GDPR Horror Story) - Michael Altfield's Tech Blog (tech.michaelaltfield.net)
submitted 2 years ago by to c/fediverse@lemmy.world
60 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 8 points 2 years ago (5 children)

Except you don't get to ignore GDPR by saying "don't expect our site to be private".

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 5 points 2 years ago (4 children)

    GDPR is really designed to target software controlled by a single entity, but this isn't that. The instances are responsible for their content, full stop. There's no way of forcing an instance to delete content, and even if there were, since the admins are running it, there's nothing stopping them from removing such a feature.

    There's also nothing stopping admins from deleting content from their servers (it's just a database, after all).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 5 points 2 years ago (3 children)

    Well then, once the EU knows about Lemmy, it'll be screwed. Again, you don't get to make excuses when dealing with GDPR. The book will be thrown at you once you have EU citizen's data, which lemmy obviously does. Saying "we made this application without it ever being possible to comply with GDPR" will only get you a bigger fine, or worse.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 2 years ago (2 children)

    "Lemmy" (the software) doesn't have any data. It all resides on servers owned by people other than Lemmy's developers. They have the user data and would absolutely be subject to GDPR.

    Again, no matter what Lemmy's devs put in place, it doesn't matter because the instance admins can do whatever they want.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •