<p>For context:</p> <ul> <li>Two big threadiverse implementors (and probably mbin) currently federate <code>Announce(Delete(Object))</code> for deletion of content — all synchronized communities follow suit and delete the content as well.</li> <li>If that object is the root-level node, and it is deleted, <em>everything below it is also deleted</em>.</li> <li>Lemmy and Piefed are investigating the possibility of changing this behaviour so that the action deletes the <em>object itself only</em>, and the reply tree stays.</li> </ul>
For context:
Two big threadiverse implementors (and probably mbin) currently federate Announce(Delete(Object)) for deletion of content — all synchronized communities follow suit and delete the content as well.
If that object is the root-level node, and it is deleted, everything below it is also deleted.
Lemmy and Piefed are investigating the possibility of changing this behaviour so that the action deletes the object itself only, and the reply tree stays.
We're in the middle of discussing how best to communicate this. With Delete(Object) behaviour shifting to deleting the single object only, there are two options to delete the entire tree/thread:
Delete(Object) with a new property with_replies or similar
Remove(Context), where Context is a new url that refers to the entire tree
Thoughts? We're discussing this tomorrow at ForumWG but it'd be nice to get some eyes on it beforehand.
cc @rimu@piefed.social @nutomic@lemmy.ml @melroy @bentigorlich
Takahe has limited support for this type: See Original Article
