# 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 11
# self = https://watcher.sour.is/conv/g2fh7na
@lyse, what's the story behind your avatar? Is that the A-Team van built out of Lego bricks?
@mckinley It's exactly that vehicle! :-) But there's not a real story behind it. In the beginning @prologic invited me to create an avatar. So after some unsuccessful deliberation I finally opened my cabinet, picked out this little feller and quickly built some scenery to take a photo. In higher resolution: https://lyse.isobeef.org/avatar-3000.jpg (yes it was dark when I took the photo)
@lyse Hah you never shared this nice story before 😅 Very nice! 👌
@lyse Hah you never shared this nice story before 😅 Very nice! 👌
@lyse Hah you never shared this nice story before 😅 Very nice! 👌
@lyse Hah you never shared this nice story before 😅 Very nice! 👌
@prologic For all the twtxt archeologists out there, that is the historic moment on how it all began. Unfortunately, yarns doesn't seem to have [all (?) of prologic's archive feed](https://twtxt.net/user/prologic/twtxt.txt/2), but somehow mine, hence only my replies show up when I search for that conversation. Quite weird. Maybe user error, no idea. But it must have been after the twt hash change, so the hashes should match, as seen by the first link in this twt. Anyways, I reconstructed that conversation by hand using the archive feeds: https://lyse.isobeef.org/tmp/avatar-story.txt
@lyse Hmm looks like you found a bug with indexing conversations that spanned across the time when we switch from #<xxxx url> to just #xxxx 🤔 I'll have to debug this...
@lyse Hmm looks like you found a bug with indexing conversations that spanned across the time when we switch from #<xxxx url> to just #xxxx 🤔 I'll have to debug this...
@lyse Hmm looks like you found a bug with indexing conversations that spanned across the time when we switch from #<xxxx url> to just #xxxx 🤔 I'll have to debug this...
@lyse Hmm looks like you found a bug with indexing conversations that spanned across the time when we switch from #<xxxx url> to just #xxxx 🤔 I'll have to debug this...