# 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/wl37mda
No-one probably noticed, but the Twtxt Search Engine has been down for several days, and I've burned all the budget (_well and truly_) already 🤣 This has been due to a data corruption event, and I've had to a) fix the data corruption and b) migrate to Bitcask v2 where I'm continuing to make reliability improvements on the KV store used in a lot of my projects.
Sorry about this, it'll be back up shortly 😅
No-one probably noticed, but the Twtxt Search Engine has been down for several days, and I've burned all the budget (_well and truly_) already 🤣 This has been due to a data corruption event, and I've had to a) fix the data corruption and b) migrate to Bitcask v2 where I'm continuing to make reliability improvements on the KV store used in a lot of my projects.
Sorry about this, it'll be back up shortly 😅
And it's back! With hopefully minimal data-loss. Generally speaking Bitcask is designed to be pretty fault tolerant, in that if a data corruption occurs, you only corrupt the last key/value pair written to the WAL (write-ehad-log).
And it's back! With hopefully minimal data-loss. Generally speaking Bitcask is designed to be pretty fault tolerant, in that if a data corruption occurs, you only corrupt the last key/value pair written to the WAL (write-ehad-log).