# 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 6523 # self = https://watcher.sour.is?uri=https://lyse.isobeef.org/twtxt.txt&offset=6396 # next = https://watcher.sour.is?uri=https://lyse.isobeef.org/twtxt.txt&offset=6496 # prev = https://watcher.sour.is?uri=https://lyse.isobeef.org/twtxt.txt&offset=6296
/short/ if it's of this useless kind. Never thought that they ever actually will improve their Atom feeds. Thank you, much appreciated!
| represent full images, . just subsequent deltas:
Original start of video
↓
|......|.....|........|......|..
↑ ↑
Cut point Cut point
Resulting video:
....|.....|........|....
↑↑↑↑
This is where it freezes
Beautiful colors after sunset
Referer altogether. But maybe this helps talking to misconfigured HTTP servers that reject requests without such a header. No clue.
connect(…) calls to ports 80, 443 and maybe whatever else has been configured in the subscription list.
Kobold in the woods
Meadows with a corn field and woodland on the hill
Backlit clouds after sunset
Moon
Lid keeps crap from falling into the upper drawer
Saws are now stored upright in their new brackets to save space
Moon
Goatpledge(…)/unveil(…)/landlock/capabilities I came across the great EWONTFIX blog, in particular this article here: https://ewontfix.com/17/ Super interesting.
returns tell me that you're not a real Rust programmer. :-D Personally, I would never omit them either. They make code 100 times more readable.
Drawers on the workbenchAlt+. is going to be my favorite one! In the above, it would also give me /dev/null, which might be probably more what I would expect.
tt. Sure, I can easily edit my feed in vim to fix typos. But then I still have to manually remove the old message from the cache so that the new message is inserted on next reload and I don't end up with "duplicates" in the message tree.
pledge(…) and unveil(…) before, right? I somewhere ran across them once before. Never tried them out, but these syscalls seem to be really useful. They also have the potential to make one really rethink about software architecture. I should probably give this a try and see how I can improve my own programs.
display() doesn't actually display it. But it's a Rust thing.
Screenshot of the message tree view
Screenshot of the reply form