# 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 5
# self = https://watcher.sour.is/conv/7xvkdaa
Using zfs on my main work drives and automatically taking snapshots hourly has saved me so many headaches.
@abucci ZFS Snapshots for what, accidently recover of deleted or overwritten data? 🤔
@abucci ZFS Snapshots for what, accidently recover of deleted or overwritten data? 🤔
@prologic they have two very useful properties. One is that yes, you can recover files at the point in time when you made the snapshot, so if you lose or overwrite a file you can get it back easily. But the other is that if you have two zpools that are in sync, you can easily send a snapshot from one to the other so that it's stored there. The two features together make for a pretty robust filesystem-level backup strategy, especially if your second pool is off site.