# 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 1
# self = https://watcher.sour.is/conv/or6pmhq
I have a dilemma. I don't know if I want my project to take longer to complete first API request but serve fresh data (it's expensive until local cache is built) or serve stale cache object immediately and trigger an update in the meantime so that next request would always be up-to-date. There's 10 to 30 minutes of interval between subsequent requests so stale data would always be visible for some time.