this post was submitted on 26 Dec 2023
-47 points (31.5% liked)

Fediverse

28262 readers
785 users here now

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!

Rules

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

founded 1 year ago
MODERATORS
ruud@lemmy.world
Xylinna@lemmy.world
MrCenny@lemmy.world
TragicNotCute@lemmy.world
automodbeta@lemmy.world
woelkchen@lemmy.world
-47
Warning: You cannot delete posts or comments on Lemmy. It stays up forever, and is in direct violation of GDPR and other national privacy laws. (programming.dev)
submitted 10 months ago by purple_mimosa@programming.dev to c/fediverse@lemmy.world
117 comments fedilink hide all child comments
 

Title says it. Apparently lemmy devs are not concerned with such worldly matters as privacy, or respecting international privacy laws.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] HKayn@dormi.zone 1 points 10 months ago (1 children)

But I think in terms of federated content, you cannot be expected to do more than send information about the deletion out. If other instances don't respect it, it's not the originating instance's job to police it.

It actually is.

When delegating the processing of PII to someone else (like another instance), you're supposed to initiate a data processing agreement with them: https://gdpr.eu/what-is-data-processing-agreement/

Unless Mastodon has somehow automated this process in inter-instance communication, they are just as liable as Lemmy is.

[โ€“] r00ty@kbin.life 3 points 10 months ago

But pii isn't being sent. A user's nickname and the domain of their instance plus any content they create is. If they choose to put their pii in public posts or user info, that's their choice but is not pii solicited in order to operate the service, it was volunteered.

It's a crucial difference. I considered this when writing the terms and data retention information for my own instance. Federation is very frugal about the information shared.