# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 30
# self = https://watcher.sour.is/conv/bd3yzvq
Great, last system update broke something, building from current master I get:


/usr/bin/ld: /lib/x86_64-linux-gnu/libm.so.6: unknown type [0x13] section `.relr.dyn'


What the heck!?

And it also appears that I'm not really able to reproduce this unread bug. It only kind of works a single time. And it has something to do with my config. Not sure what it is yet. I also noticed that the <updated> timestamps in the entries somehow shifted between the old and new feed. Da fuq!?
The binutils upgrade fixed that linking issue. Phew!
@lyse Hmmm where's the root of this thread? 😆
@lyse Hmmm where's the root of this thread? 😆
@lyse Hmmm where's the root of this thread? 😆
@lyse Hmmm where's the root of this thread? 😆
@prologic Hmmm, for some very weird reason yarnd computed another hash: https://twtxt.net/twt/cxpxroa That's the tree in tt with highlighted hash bd3yzvq in white background:

Conversation tree in tt

What do other clients see here? Which hash does that linked twt produce on your implementations?
@prologic Alright, there's some erroneous markdown parsing going on, I reckon. In my original twt I have a code block surrounded by three backticks. The code block itself contains a single backtick. However, at least for rendering, yarnd shows three backticks instead (not sure if my markdown is invalid, though):

Not matching markdown in tt and yarnd
@prologic Also, yarns shows the same markdown tripple backtick expansion in the code block: https://search.twtxt.net/search?q=%22%2Flib%2Fx86_64-linux-gnu%2Flibm.so.6%22&f=
@prologic That's only one part of the issue. When I tripple the backticks the resulting hash is fmefkga, still different. So there must be also something additional going on.
@lyse FWIW, the thread looks like this for me: https://movq.de/v/82c2a8a8cf/s.png
@lyse FWIW, the thread looks like this for me: https://movq.de/v/82c2a8a8cf/s.png
@lyse FWIW, the thread looks like this for me: https://movq.de/v/82c2a8a8cf/s.png
@lyse FWIW, the thread looks like this for me: https://movq.de/v/82c2a8a8cf/s.png
@lyse interesting... ill look into the parsing on that one
@lyse interesting... ill look into the parsing on that one
@lyse interesting... ill look into the parsing on that one
@lyse interesting... ill look into the parsing on that one
@lyse WTH.. i cant reply to this?
@lyse WTH.. i cant reply to this?
@movq Perfect, that's looking correct. At least both our clients agree. :-) Thanks for verifying. @xuu You actually replied to the correct thread. :-)

Xuu replied correctly, without noticing
@xuu is our man, he's killing it today! <3 He fixed the lexer and also prepared a new yarnd version. Testing it locally, it works like a dream:

Conversation showing properly

Now that I updated my feed with this twt, all yarnd caches should hopefully receive a new twt with the correct hash, once they refetch my feed.
@lyse Yup for some reason I can see the root of this yarn now 🤗
@lyse Yup for some reason I can see the root of this yarn now 🤗
@lyse Yup for some reason I can see the root of this yarn now 🤗
@lyse Yup for some reason I can see the root of this yarn now 🤗
nice work guys 👌
nice work guys 👌
nice work guys 👌
nice work guys 👌