# 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 8
# self = https://watcher.sour.is/conv/pizpbda
lyse
lyse.isobeef.org
View Thread
Something is wrong with me. My eyes fell on the onions and I thought, mmmmm, those apples look delicious. But I'm now eating a real apple.
movq
www.uninformativ.de
View Thread
@lyse What?! 😂 Time for bed!
movq
www.uninformativ.de
View Thread
@lyse What?! 😂 Time for bed!
movq
www.uninformativ.de
View Thread
@lyse What?! 😂 Time for bed!
prologic
twtxt.net
View Thread
I reckon 😂
prologic
twtxt.net
View Thread
I reckon 😂
prologic
twtxt.net
View Thread
I reckon 😂
lyse
lyse.isobeef.org
View Thread
ARGH! All tests passed, but once I ran the exact same scenario in the real application, numbers didn't line up anymore. What the heck, how in the world is this even possible!? Turns out I haven't committed the changes to the database, that's why I still could see them perfectly fine in my debug session, but the application's session of course didn't. Took me four (!) hours to figure this out. Yeah, I really have to go to bed now. Good night.