# 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/fuwuuoa
{@https://twtxt.net/user/prologic/twtxt.txt>#iirgl5q} @adi @lyxal (#tbcxz5a) That depends... If you are building static binaries, I _would_ agree with you. But deploying complex software on bare-metal or virtual-machines is actually quite error prone and not very portable at all. Docker (_if it did anything at all_) really shined in what I call a really really good "packaging model" and build tooling. This is now called the OCI Spec. Caching and CoW (_copy-on-write_) or OverlayFS + SHA255 of layers is a wonderful ting for portability.