# 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 4
# self = https://watcher.sour.is/conv/hv7xxjq
I _think_ my new SqliteCache is almost ready for prime time 🤞
There are however a few implications to note:
- It will be possibly to page through much larger quantities of twts per feed, this is potentially unlimited (_depends on disk space_)
- Automated Feeds (_bots_) like @tiktok will now behave/display very differently. You will see all it's historical Twts, whereas before you'd only see the one because the MemoryCache's behavior was to "replace" Twts.
I'm _hoping_ everything else remains the same and true to what we've collectively built and to spec. Replies work, Forks work, various views, filters and so on still work. I'm developing this new cache in a way that uses a "delegate" pattern and a double read / double write with metrics so I can over time see that none of the "old cache" is used anymore.
I see nothing wrong with the "implications". I would call them features. I think this will be the best thing that happened to Yarn since the subject extension.