- cross-posted to:
- fediverse@lemmy.ml
- fediverse@kbin.social
- cross-posted to:
- fediverse@lemmy.ml
- fediverse@kbin.social
Highlighting the recent report of users and admins being unable to delete images, and how Trust & Safety tooling is currently lacking.
You must log in or register to comment.
The issue I see is that if my instance is on the hook for the fediverse at large, and I operate on an allowlist basis, malicious actors can scrape PII and ignore the GDPR, and that would make me the one on the hook for that, isn’t that right?
There is plenty of jurisprudence and clarity needed, so… maybe. Hence the importance for the framework itself to be as GDPR compliant as possible and not store PII if not nessecary and remove it once no longer nessecary. (Storing someone’s IP for login, and post validation, bans etc should be limited to the period that makes sense, not infinitely.)
And in your example, the ‘malicious’ part of the 3rd party probably makes it different. Maybe then it is a dataleak.
