It’s been like that for as long as I can remember … Why do we love misery so much?
It’s really turning me off lately, making me want to leave IT for good. 😒
# 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 363 # self = https://watcher.sour.is?uri=https://uninformativ.de/twtxt.txt&offset=63 # next = https://watcher.sour.is?uri=https://uninformativ.de/twtxt.txt&offset=163
bind log:dig +trace … ends with:
yarn
yarn social


… I’ve used that quite a lot, too. 😅 As for entering that stuff directly: https://en.wikipedia.org/wiki/Compose_key is great

url metadata field into account (if present)?
access.log. It’s not polished enough to be published, though.
https://uninformativ.de/twtxt.txt, which is not correct. The www. is missing. Is there something we can do about that or should I extend my client so that it recognizes this as “me”, too? 😅
unless statement


curl says:
Last-Modified: Fri, 02 Sep 2022 21:38:02 GMT
2022-09-02T22:31:26-00:00
Last-Modified is correct (it probably is, unless her server’s clock is off, which is less likely than a bug in the script), then the latest twt looks indeed like it was from “the future”.


binfmt_misc in action. Drew DeVault happened to mention binfmt_misc yesterday, too, in a different context. I don’t really do cross-architecture stuff … This topic only popped up at work, because Apple introduced their ARM M1 CPU and now our devs build multiarch Docker images (and we were wondering how the heck QEMU got installed).