@thisismissem@hachyderm.io in a post yesterday brought back the idea that better post controls could be achieved if the reply were sent to the target only, and the target then forwards it if applicable.
It reminded me of @trwnh@mastodon.social's https://w3id.org/fep/7888, which attempts to govern a similar flow where a reply is sent to the context owner (instead of inReplyTo, which I think was Em's intent), and the context owner (and/or originating server) federates out an Add if approved.
Which got me thinking about whether that federated server could actually send out a Remove too!
Let's say a reply is made but later on, a mod decides that it is to be deleted. A Remove would be a way to signal to other instances that the content actually be removed/deleted!
We could even take it one step further; servers will always exist who don't adhere to the philosophy of the context owner approving replies. If they federate their own replies out, the context owner could actually proactively send a Reject and limit the spread of those replies...
@julian@thisismissem if you just check the replies/context collection directly then it doesn’t matter which other posts might exist but haven’t been added.
if you as a client are aware of a reply/threaded-post outside of those collections, then it would be best to consider it “singly linked” — navigating from the post to the parent/thread is possible, but then the post would effectively not be visible from those views.
@julian@thisismissem if you just check the replies/context collection directly then it doesn’t matter which other posts might exist but haven’t been added.
if you as a client are aware of a reply/threaded-post outside of those collections, then it would be best to consider it “singly linked” — navigating from the post to the parent/thread is possible, but then the post would effectively not be visible from those views.