(#wkjlotq) Sorry I’m not sure what you’re saying here… Twt Hashes are very consistent

@lyse (#wkjlotq) Yeah as discussed on IRC we don’t need to expand Twt Hashes into the feed anymore but just let clients linkify them client-side as some UX feature ; e.g link to a search instance

(#wkjlotq) @fastidious > How about @lyse ? @lyse 's client is doing the _right_ thing : ``` 2021-10-15T23:30:00+02:00 @ (#lhi6wda) Sure. I'm currently just supporting Markdown links to include them in the URLs view so I can operate on them. Media still show the bang in front of them. But it's good enough for now. ;-) ```

I am noticing that Yarn doesn't treat "outside" (that is, twts coming from a client other than Yarn) twts hashes right. Two examples: - - There are many more, but those two will give you the gist. Yarn links the hash to the poster's twtxt.txt, so conversation matching will not work.

@movq (#wkjlotq) Oh, OK, then not touching it. I will consider it part of history and, thus, unchangeable. 😊

(#wkjlotq) I’m only seeing this happen on replies from @movq and @quark 🤔

(#wkjlotq) Should be fixed on jenny’s `main` now. 🥳