@zvava That was my greatest concern with how it is currently handled, I'm afraid to break threads even by fixing a typo.

Handling it via the pod might work but I think it's not the best approach, external feeds and clients don't usually use a pod api but their own implementation, so any workaround won't work there.

That's why my proposals addressed those issues:

• the idea of using a "key" instead of the url (with the url as a fallback), the key could even be a public key so it can be used verifieable in crypto functions
• using the timestamp to prevent content changes to break threads (plus being simpler to implement)
• using an explicit thread reference with an alternative subject format (like [<a href="?search=THREAD_ID" class="tag">#THREAD_ID</a>] Hello world and replies with (<a href="?search=REPLY_ID" class="tag">#REPLY_ID</a>) Ahoy) so the content can change without affecting the thread reference, and anyone can use their own schemes freely