- cross-posted to:
- technology@beehaw.org
- fediverse@kbin.social
- fediverse@lemmy.world
- cross-posted to:
- technology@beehaw.org
- fediverse@kbin.social
- fediverse@lemmy.world
Highlighting the recent report of users and admins being unable to delete images, and how Trust & Safety tooling is currently lacking.
Maybe encryption can help? Instances only copy the encrypted image, and only the original instance provides the encryption key to client apps. This way, the original instance can de-facto delete the image copies by simply refusing to issue the key.
It also means the content is “lost” from all instances if the original server goes down, which altogether with the need to cache the key to continue to provide the service basically means you’ve just implemented DRM on top of Fedi.
And that’s fine. If one instance has to be able to delete one revenge child porn from all the instances, it has to be what you call a DRM. Also, don’t cache the key because that’s exactly the opposite of what this is meant for.