# 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 6
# self = https://watcher.sour.is/conv/hk4wqyq
@kat I've almost fixed this btw ðĪ Just testing it thoroughly and polihsing the code. In case you're curious, I do this style of development called "Observability Driven Development" (ODD) whereby I make observations of the system via metrics and internal observations and adjust the system's overall behavior to the desired outcome ð
@prologic ODD, lol. I don't wanna be rude, but this sounds more like Code And Fix.
@lyse Well you are being _slightly_ rude ðĪŠ Sure you could write unit tests for this, but in practise testing emergent properties and behaviors of a system is actually a lot harder than you might realize. But I'm happy to always be proven wrong ð
I'm not even being facetious here either. I'd llove to see you "unit tests" this: 
@prologic To clarify, from my observations on how the system behaves, it feels like that. This doesn't make it any better, I know. Sorry mate! I never claimed that testing is always easy, but in my experience it sure does help cutting down regressions. But to each their own, no worries. The diagram is all Greek to me. Anyway.
@bender True.
@lyse You are of course right! ðĪĢ There are some low level components that can and should be unit tested for sure! ð