Oddbean new post about login | logout When a thread turns into a chat, it makes sense to display it as such. This usually starts to happen from the second level of replies to a post. #nostrdesign https://cdn.satellite.earth/59a0f06770b1eb23557fc74702164cef378868004bb5642db00df524106aa859.png nostr:nevent1qvzqqqqqqypzp75cf0tahv5z7plpdeaws7ex52nmnwgtwfr2g3m37r844evqrr6jqqsq4c4v3dl5rfs4eff9a22g9e6n9seehc4jp5ln7s4p2d3qa5q5hlqt8klsw
there can be sequence problems sometimes, the solution would be to tag both the next level up and the current node as you are composing
Not if you display everything chronologically (like a chat).
when i was starting building the chatbot i frequently had problems with #coracle chat rearranging the sequence of the messages if they were 1 second or less separated adding a pair of context links would make it resistant to being rendered out of sequence
Aaah, I see. To be clear: you mean adding those links in the background or in the front end?
the client should do it, attach one tag to the immediate previous and one to the next level up yes, otherwise it is a mess, trees get nasty when they get long, losing context
just to be clear what this is, is a causality chain... the multiple messages in the same segment are naturally not sequential, but everything else should be, and linking to the tree upwards as well as the previous branch ensures that timestamps don't rule the rendering order, because replies are causal, not sequential if you are not making a tree then you trust the timestamps but because they are applied by the client you have a problem where users can mangle things with slow clocks, and adding this causal chain ensures that the client has multiple options to delineate sequence and association
