…#v5yaeha) @anth @lyse @movq Actually... I _think_ we could change the Twt Hash extension a bit here and remove the need to fully qualify and expand them into full URLs. The reason we did that in the f…

…#v5yaeha) Sorry for the _very_ delayed response (_I've been sick all week :/_), but I just remembered that one of the benefits of using full URLs for Tags or Twt Hashes (_which are themselves tags_) i…

…#v5yaeha) @movq As for developing a Twtxt 2.0 spec/format/protocol, I'm not sure. On one hand @buckket _seems_ to be quite upset that we've used his format/spec and named a "codebase" with a similar/i…

…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…

… @darch @xuu @anth (#v5yaeha) Ah, I understand that, anth. But the noisy mentions alone make it quite terrible to read the raw form, so I really wouldn't want to refrain from a client folding them. Be…

…e (#v5yaeha) 100% agree. Fun fact: Couldn’t we actually do that? I mean `timestamp \t twt-id \t reply-id \t text`. Older clients would just include the IDs in the message, but they wouldn’t break. (I …

…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 …