awt[asciilifeform]: !!ticker btc usd
deedbot[asciilifeform]: $29,086
awt[asciilifeform]: asciilifeform: in your gui, how are you displaying threads?
awt[asciilifeform]: Is every message except the very first on a net on a thread?
awt[asciilifeform]: Or are there multiple "root" messages?
awt[asciilifeform]: I guess any message without an antecedent should get it's own root until an antecedent is found.
asciilifeform: awt: only got as far as linear display (by chain) toggleable w/ strictly chronological
asciilifeform: where w/out antecedent -- shown chronologically
asciilifeform: and yes inevitably 'multiple roots' (how else, if >1 w/out antecedent)
asciilifeform given as not has actual working 'engine' yet, tested strictly w/ canned msgs
awt[asciilifeform]: Not entirely sure how to handle root selection for sending new messages. If every message is a reply to the previous, the thread could get very deep, which causes display issues.
awt[asciilifeform]: Could perhaps have a configurable depth limit and add new roots once exceeded with some sort of affordance to navigate to the antecedent.
awt[asciilifeform]: Could have a sort of "mixed" view where "replies" are a series of messages that all use the same antecedent and are displayed chronologically *under* that single message when expanded.
awt[asciilifeform]: Or alternatively, top level linear display but an affordance to "view/reply" in context where you get a tree view, with notifications and/or annotations for messages with antecedents > configurable age that may be off the page.