@anth (#3oomzpq) What window manager are you using and what did your daughter teach you? :-)

@anth (#l6klv2q) Why? What happened? 🤔

@anth (#5e3pqpa) Brilliant! 🤣

(#l6klv2q) @anth Yeah me neither Way back when, when it first started, I mined a few BTC with some Butterfly hardware until it got too "difficult" that I just stopped, because it was either purchase more hardware or bigger/better hardware or stop. Somehow I had a gut instinct all those years ago to pull out. Thank goodness I did because BTC is now one of the worst ecological disasters of the modern dage!

@anth (re Hash Tags) you just need to improve your client. The alternative is this particular Twt itself. We formalized and documented this too as Twt Subject Extension. But then extended it further as hashes are a good way to globally and uniquely address individual posts. But up to you 🤷‍♂️

@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 @dbohdan for the initial work on Twt Hash(es) really, and @lyse for making a a format document for it!

@anth @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, anth?

(re: #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 code-thing is a reply or is in relations/reaction to something else (re: #v5yaeha) **EDIT:** right now the twt.social client does not allow you to move the (#v5yaeha) ...

(#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 matter of stripping out the "Twt Subject" out now from the presentation layer. But somehow I don't think @anth is talking about this, or is using an old client with a more bland UX?