# 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 10
# self = https://watcher.sour.is/conv/jdlvdwq
@support Interestingly, I too lost data / twts, but it isn't immediately obvious because our peer pods seem to be replicating some or all of those.
@jlj How did you rehome the pod? rsync tar?
@jlj How did you rehome the pod? rsync tar?
@jlj How did you rehome the pod? rsync tar?
@jlj How did you rehome the pod? rsync tar?
@prologic In effect, yeah. Lost some twts despite not much time between; wondering whether I should've taken advantage of those job functions for pod owners first, to sync the backend, for example.
@jlj Hmmm, to be honest I'm not sure how you'd have lost any data at all really. 🤔 Can you elaborate on what you think you lost, maybe point me to a twt you think has gone missing or something? I mean there's an in-memory cache, that is synced to disk periodically (and on shutdown), but the cache is really ephemeral anyway, it is populated by fetching feeds. Then there's the on-disk archive, which really shouldn't suffer any data loss, as it's only ever written once.
@jlj Hmmm, to be honest I'm not sure how you'd have lost any data at all really. 🤔 Can you elaborate on what you think you lost, maybe point me to a twt you think has gone missing or something? I mean there's an in-memory cache, that is synced to disk periodically (and on shutdown), but the cache is really ephemeral anyway, it is populated by fetching feeds. Then there's the on-disk archive, which really shouldn't suffer any data loss, as it's only ever written once.
@jlj Hmmm, to be honest I'm not sure how you'd have lost any data at all really. 🤔 Can you elaborate on what you think you lost, maybe point me to a twt you think has gone missing or something? I mean there's an in-memory cache, that is synced to disk periodically (and on shutdown), but the cache is really ephemeral anyway, it is populated by fetching feeds. Then there's the on-disk archive, which really shouldn't suffer any data loss, as it's only ever written once.
@jlj Hmmm, to be honest I'm not sure how you'd have lost any data at all really. 🤔 Can you elaborate on what you think you lost, maybe point me to a twt you think has gone missing or something? I mean there's an in-memory cache, that is synced to disk periodically (and on shutdown), but the cache is really ephemeral anyway, it is populated by fetching feeds. Then there's the on-disk archive, which really shouldn't suffer any data loss, as it's only ever written once.