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

…#v5yaeha) Or is it? Discoverability is an issue with twtxt. Without the URL, I have absolutely no idea which thread this might belong to *if I’m reading a completely new feed*. But with the URL, I can…

(#v5yaeha) Indeed, using the shortest form possible (see this twt) would be nice. I’ll change my client accordingly. 👍

@prologic @anth (#v5yaeha) Sounds like a good idea. The hash to conv/search url should stay local to a pod.

@prologic @anth (#v5yaeha) Sounds like a good idea. The hash to conv/search url should stay local to a pod.

(#v5yaeha) @anth Yeah we've always supported both forms. @xuu shall we stop fully expanding tags out?

(#v5yaeha) @prologic Looks like twtxt.net is already happy with it, so that's good! I'm just going to aim for that.

(#v5yaeha) @prologicFor example, this should work (no idea if it does).

(#v5yaeha) @prologicYes, I think tags should just be #foo, and let the client figure out searching if it cares.

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