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

…ogic @lyse @darch @xuu (#v5yaeha) Yes, the presentation layer can fix a few things. My client hides the subjects completely to save space and I rarely care about the exact hashes. For debugging they c…

…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) @movq I _really_ appreciate you saying this! Thank you! 🙇‍♂️ To be fair @anth we just took something that we were observing happening in the real-world and "formalized" it. You can thanks @d…

…#v5yaeha) If we're strictly talking about about presentation / UX issues here, @xuu already largely solved this already in changes to how the parser works. See for example: It would just be a mat…

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