# 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 21
# self = https://watcher.sour.is/conv/tbcxz5a
@lyxal I _should_ do the same shortly... 🤣 But I'm hacking on box 😴
@lyxal I _should_ do the same shortly... 🤣 But I'm hacking on box 😴
@lyxal I _should_ do the same shortly... 🤣 But I'm hacking on box 😴
@prologic @lyxal box is pretty cool, although personally, I'm not a big fan of containers.
@prologic @lyxal box is pretty cool, although personally, I'm not a big fan of containers.
@prologic @lyxal box is pretty cool, although personally, I'm not a big fan of containers.
@adi @lyxal Oh? Why's that? 🤔 They're just Linux Namespaces afterall...
@adi @lyxal Oh? Why's that? 🤔 They're just Linux Namespaces afterall...
@adi @lyxal Oh? Why's that? 🤔 They're just Linux Namespaces afterall...
@prologic @lyxal Not a big fan of deploying inside a container, I think it may hide unresolved portability issues and leads to less robust code? Prefer to deploy to "bare metal"?
@prologic @lyxal Not a big fan of deploying inside a container, I think it may hide unresolved portability issues and leads to less robust code? Prefer to deploy to "bare metal"?
@prologic @lyxal Not a big fan of deploying inside a container, I think it may hide unresolved portability issues and leads to less robust code? Prefer to deploy to "bare metal"?
@adi @lyxal 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.
@adi @lyxal 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.
@adi @lyxal 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.
Containers themselves OTOH have been around for the longest time, they were just made "popular" so to speak by Docker. They existed in the form of BSD Jails (_still do_), then OpenVZ for LInux, then LXC then Linux Namespaces in general (_now part of the Kernel along with CGroups_) and popularized by Docker and Kubernetes.
Containers themselves OTOH have been around for the longest time, they were just made "popular" so to speak by Docker. They existed in the form of BSD Jails (_still do_), then OpenVZ for LInux, then LXC then Linux Namespaces in general (_now part of the Kernel along with CGroups_) and popularized by Docker and Kubernetes.
Containers themselves OTOH have been around for the longest time, they were just made "popular" so to speak by Docker. They existed in the form of BSD Jails (_still do_), then OpenVZ for LInux, then LXC then Linux Namespaces in general (_now part of the Kernel along with CGroups_) and popularized by Docker and Kubernetes.
@prologic @lyxal I'm in a small and simple phase. Used to do NodeJs and PHP before, don't remember using containers for deployment either we weren't or I wasn't in charge of the deployment.
@prologic @lyxal I'm in a small and simple phase. Used to do NodeJs and PHP before, don't remember using containers for deployment either we weren't or I wasn't in charge of the deployment.
@prologic @lyxal I'm in a small and simple phase. Used to do NodeJs and PHP before, don't remember using containers for deployment either we weren't or I wasn't in charge of the deployment.