@anth (#v5yaeha) I was reluctant, too, at first, but proper threading seriously improves the twtxt experience. This should have been built-in from the start.

…#v5yaeha) @movq I _really_ appreciate you saying this! Thank you! 🙇‍♂️ To be fair @anth we just took something that we were observing happening in the real-world and "formalized" it. You can thanks @d…

…movq @prologic (#v5yaeha) The hashes are certainly not very elegant, but as an afterthought make the twtxt universe much more pleasant as movq said. Are you really reading the twts in in its raw form,…

(#v5yaeha) @lyse How _could_ they be made "more elegant"? 🤔 Is it just a presentation thing? (UX)?

…: #v5yaeha) @prologic @lyse @anth One way to make the raw txt easier to read would be to move the (hash) to the end of the line. Another thing would be to add `re:` to it so it would be cleared that c…

…#v5yaeha) If we're strictly talking about about presentation / UX issues here, @xuu already largely solved this already in changes to how the parser works. See for example: It would just be a mat…

…client does not allow you to move the (#v5yaeha) … No it does not. 🤣 Its meant to be "idiot proof"! Recall that the goal here is to bring the simplicity of what Twtxt provides to the masses. There's…

…h @prologic (#v5yaeha) Technically it should be at the start.. Though the parser doesn't currently care where it is. Though that leads to artifacts like any random string inside perens becoming a subj…

…gic @darch @xuu (#v5yaeha) In my opinion twt hash and subject ideally would be dedicated fields in a twt, similar to `Message-ID` and `In-Reply-To` e-mail headers. Something like `timestamp \t twt-id …

…ogic @lyse @darch @xuu (#v5yaeha) Yes, the presentation layer can fix a few things. My client hides the subjects completely to save space and I rarely care about the exact hashes. For debugging they c…