TNO Threading (draft):
Each origin feed numbers new threads (tno:N). Replies carry both (tno:N) and (ofeed:<origin-url>). Thread identity = (ofeed, tno).

• Roots: (tno:N) (implicit ofeed=self).
  
• Replies: (tno:N) (ofeed:<url>).
  
• Clients: increment tno locally for new threads, copy tags on reply.
  
• Subjects optional, not required.
  

…

(#vdkllnq) Example:

Alice starts thread #42:

2025-09-25T12:00:00Z (tno:42) Launching storage design review.

Bob replies:

2025-09-25T12:05:00Z (tno:42) (ofeed:https://alice.example/twtxt.txt
) I think compaction stalls under load.

Carol replies to Bob:

2025-09-25T12:08:00Z (tno:42) (ofeed:https://alice.example/twtxt.txt
) Token bucket sounds good.

(#vdkllnq) This is possibly the only other threading model I can come up with for Twtxt that I think I can get behind.

(#vdkllnq) @prologic@twtxt.net That’s a completely flat threading model (you can’t reply to replies). Is that intentional?

(#vdkllnq) @movq@www.uninformativ.de Yes it’s kind of terrible 😞 – Let’s not do this 🤣