# 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/qc7mavq
{@https://twtxt.net/user/cvshumake/twtxt.txt>#ssmj7da} @prologic (#tgmogmq) this is to say, FEC & data duplication solve different problems. Disaster Recovery is possible with data duplication, but a bug in your FEC code and no duplication will prevent it. Use case matters because is your def of HA going to be 99.99% or 99.999%? The first can be single-instance mysql. The second, a cluster. More, and you start stepping into things like TiDB or Spanner.