@xuu Yes! I _think_ if we scope out some more inter-pod (_let's call it "federation"_) features we _could_ probably improve the experience a lot here. The core bits are there, we just need to extend them. The biggest thing for me right now is refactoring the internal eventing around User-Agent detection and on-Pod Follow/Unfollow. If we can refactor that we'll have a good base to work on and build more inter-pod features.
@vain Yeah cool! I really like the TUI style a lot! Iโm very happy to see more clients take on our small extensions that make the experience jusf that little bit better ๐
I suspect once you do and your pod pulls in his feed the hashes will then exist on your pod and the conversation links will then work for that conversation
@vain@lyse we plan to make changes upstream to both test and txtnish and any other actively maintained client, but Iโm afraid twtxt the original client might not get these features as it seems to be unmIntaimed ๐ฅ
On the search engine madness going on...\n\n> if I use Google, they will present Google results first. That's my choice/tradeoff. But forcing them to present things that I have no interest in, and which I could find in 10 seconds if I wanted to seek them out, is just breaking the search engine as far as I'm concerned.\n> I will likely - like paid listings - never use this news showcase junk. If I think that the search engine of my choice wasn't returning the things I want, or returning things that I don't want, then I'll go to another.\n> Google won the search wars initially by returning the most relevant of results with the least amount of spam. It's a hard job in the modern age. They were so good at it, it made them one of the largest companies in the world on the back of a pittance of advertising revenue per search.\n> And now you want to tell them what should be most relevant on their search engine?
I don't get it. This document says nothing about what BlueSky is or what is being proposed here. This document quite literally (_and admittedly I've only read parts of it and skimmed the rest_) just describes a bunch of other well-known protocols and some new ones, how they work and various properties. The sad thing I find it some of the protocols mentioned are in fact "messaging" protocols and have little to nothing to do with "social networking" per se, at least in the documented and well understood model as documented.
@xuu@thewismit As I said on IRC, the session cookie is getting dropped somehow ๐ฅ trouble is I havenโt used NGINX in a while so Iโm a bit out of touch ๐
Cool so you have another twtxt feed? ๐ Maybe you could help bring our twt CLI up to speed so we get the best of both worlds, i.e: you can then sync your other feed here, that was the idea anyway, have a cli twt that behaves like a traditional twtxt command-line client with a few optional extras like login and sync which would login/sync to a chosen pod like mine here.
@ionores yeah as I said I donโt think Iโve ever seen one before! My being blind means I miss out on a lot of things in the world ๐ \n\nif you happen to have any good pics of a nice looking sparrow close up feel free to share them! ๐
@sorenpeter@darch I _think_ your PHP Twtxt client on your website is missing an important feature:\n\n- Expanding @mention to their proper form @<nick url>. This is what every client should be doing as part of their pre-processing step.\n\nDoes your client have the concept of a "Following" list? Where you keep a list of feeds you are following?
\n\n#AustraliaZoo
\n\n#AustraliaZoo
\n\n#AustraliaZoo
\n\n#AustraliaZoo
\n\n> Guy says to his colleague โjust donโt fall in!โ She replies โyeah good advice!โ\n\n๐คฃ\n\n#AustraliaZoo
\n\n#AustraliaZoo
\n\n#local #art