Replies belong to their authors
The default idea is that a reply is published on the reply author's own feed. The original publisher may display that remote reply as part of a conversation, but does not become the authoritative storage location for it.
That immediately creates real questions
Verification
How does a site establish that a remote URL actually authored the reply being presented?
Change and deletion
What should happen if the remote reply changes or disappears?
Spam and abuse
Independent publishing must not mean that anybody can force arbitrary content into somebody else's presentation.
SSRF and fetching
Any design that asks servers to fetch arbitrary remote URLs has to treat server-side request forgery as a first-class security issue.
Moderation remains local
A site owner can refuse, hide, block, or moderate remote participation on their own site without erasing the remote author's copy from the remote author's feed.
Conversation without custody
Participating in a conversation does not require surrendering custody of your words to the server where the conversation began.
← Back to the landing page