No it combines the concepts of starting a new thread from a…
No it combines the concepts of starting a new thread from an existing thread and replying to an existing thread in a totally unintuitive way, and degrades either experience because of it. Other platforms optimise for one or the other and lean in to the benefits of that.
Think GitHub/StackOverflow vs X/Threads
@treechat tries to be both and thereby succeeds at neither imo. And basic features seem deprioritised. @mention didn’t work again.
Replies
i think the closest model is slack, but with more than one level, so in slack every message can become a thread
Okay great then I suggest you copy the ux of slack
i do actually agree that this tension of "where to reply" current thread or branch is a big ux challenge from a design and user comprehension perspective
cc @arghzero