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

(#v5yaeha) @movq No argument that threading is an improvement. But I think (#hash) does that, and I think figuring out how to search should mostly be up to the client.

(#v5yaeha) I agree clients should present things better (part of why I'm writing one!). But that should be additive. There's a reason we're not passing json around.

(#v5yaeha) And just to be clear, without the work on twtxt.net by @prologic and you other people, twtxt would be very very dead now. That would be a shame. I really appreciate your efforts!

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

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

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

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

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