…#v5yaeha) In addition we (@xuu and I) are looking to start building out support for Distributed Tags which will make this whole thing make a lot more sense -- At least between pods, but even regular t…

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

…h @xuu @anth @jlj (#v5yaeha) I'm composing in raw form, too. While this works quite nicely, I certainly don't want to have to read all of them in raw. Maybe I should take a look at implementing some k…

…#v5yaeha) Fun fact, I always feed twts in their raw form. Was a bit noisy at first, yes, but I got used to it really fast. 🤔 Not to say there’s no room for improvement, but it’s also not a complete di…

…#v5yaeha) I agree! But it’s a trade off. how exactly would clients figure out how to do the searching on their own? without some hints like full URI‘s I don’t really see this benefiting clients at all…

(#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) @prologic Exactly, but that reduces the argument for URLs in the post. The client should figure out how to search based on the hashtag.

…#v5yaeha) Another thought... The way the tags and the parser @xuu wrote works now, is that, one day we might be able to change the URL they point to, to say a search engine rather than the source pod …

…#v5yaeha) The point re discoverability is an important one. I have to admit I didn't think of that myself, funny how things get used unexpectedly. 😀 As @lyse points out I _would_ think about changing …

@prologic @vain (#v5yaeha) This captures my sentiments on both points absolutely perfectly! 😁🤗