In-reply-to » @prologic When I first started using twtxt, I was fascinated by the fact that itā€™s just a simple text file. This is already undermined a lot today by us using multiline replies and Markdown and what not. Still, I would love to retain this property of it being just a file that needs very few external tools to maintain. (Jenny is quite bloated, one might argue. One of the reasons for even starting the jenny project was the calculation of hashes ā€“ I was using a smaller, simpler toolchest before.)

@movq@www.uninformativ.de So I obviously happen to agree with you as well. However in so saying, one of my goals was also to bring the simplicity of Twtxt to the Web and for the general ā€œlay personā€ (of sorts). So I eventually found myself building yarnd. Has it been successful, well sort of, somewhat (but that doesnā€™t matter, I like that itā€™s small and niche anyway).

I agree that the goal of simplicity is a good goal to strive for, which is why Iā€™m actually suggesting we change the Twt identifiers to be a simple SHA256 hash, something that everyone understand and has readily available tools for. I really donā€™t think we should be doing any of this by hand to be honest. But part of the beauty of Twt Subject and Twt Hash(es) in the first place is replying by hand is much much easier because you only have a short 7 or 11 character thing to copy/paste in your reply. Switching to something like <url> <timestamp> with a space in it is going to become a lot harder to copy/paste, because you canā€™t ā€œdouble clickā€ (or is it triple click for some?) to copy/paste to your clipboard/buffer now šŸ¤£

Anyway I digressā€¦ On the whole edit thing, Iā€™m actually find if we donā€™t support it at all and donā€™t build a protocol around that. I have zero issues with dropping that as an idea. Why? Because I actually think that clients should be auto-detecting edits anyway. They already can, Iā€™ve PoCā€™d this myself, I think it can be done. I havenā€™t (yet), and one of the reasons Iā€™ve not spent much effort in it is it isnā€™t something that comes up frequently anyway.

Who cares if a thread breaks every now ā€˜n again anyway?

ā¤‹ Read More