The solution: A three‑layer deletion model This is the only model that satisfies both Lemmy’s architecture and user expectations.
Layer 1 — Local hard deletion (guaranteed) When a user deletes a post/comment:
the content is wiped from their home server
the object can remain as a placeholder to preserve thread structure
media files are fully removed
This part is already possible.
Layer 2 — Federated delete signal (best‑effort) When deletion happens, the home server sends a message:
“This content is deleted — purge your copy.”
Servers that respect federation will:
delete their cached copy
update the thread
remove the content from search
Servers that don’t care will ignore it — but that’s already true today.
This is the missing piece Lemmy needs to implement.
Layer 3 — User‑initiated purge request (optional escalation) Admins already have a purge tool that:
deletes content locally
sends a federated purge request
is accepted by most servers
Expose this to users in a controlled way:
rate‑limited
confirmation required
optional admin approval
This gives users real deletion power without enabling abuse.
Thanks for the clarification — that helps me understand the current behavior much better. I didn’t realize Lemmy already sends a proper ActivityPub delete signal, and it makes sense that different servers handle it differently.
From a user perspective, the part that still feels incomplete is that deleted posts and comments remain visible as “deleted by creator,” even when the content itself is gone. I understand why the object can’t be purged instantly for moderation reasons, but it does create the impression that deletion isn’t really happening.
What I’m hoping for is a more user‑friendly deletion experience — something that preserves moderation needs and federation realities, but still gives users a clearer sense of control over their own content. Even if perfect deletion across all servers isn’t possible, improving the local UX would go a long way.
I appreciate you taking the time to explain the technical side.