yarn.meff.me @<movq https://www.uninformativ.de/twtxt.txt> "(#xrswtvq) @zvava > `(#abcdefghijkl https://example.com/tw.txt#:~:text=2025-10-01T10:28:00Z)`, because it can be simply hacked in to clients currently on hashv1 and provides an off-ramp to location-based addressing I like that property (an off-ramp to location-based addressing), so I think I could live with that approach. ✅ (I’m not sure why we’re using text fragments, though. Wouldn’t that link to the first occurence of `2025-10-01T10:28:00Z`? That’s not necessarily correct. And, to be proper URLs that Firefox and Chromium understand, it would also need to be written as `2025%2D10%2D01T10:28:00Z`. [The dash carries meaning](https://wicg.github.io/scroll-to-text-fragment/#context-terms), sadly. I think all this just creates needless complication. How about we just go with `https://example.com/tw.txt#2025-10-01T10:28:00Z`?)"

Yarn

Recent twts in reply to #ohd4guq

movq @www.uninformativ.de

Wed 1, 5:50PM (1d ago)

(#lolhvka) @zvava@twtxt.net Hm, I tried with https://www.uninformativ.de/twtxt.txt#:~:text=2025-09- and my Firefox 143 didn’t like it. https://www.uninformativ.de/twtxt.txt#:~:text=2025%2D09%2D worked. 🤔

#ohd4guq

Login to participate in this yarn.