# 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/6uqp3cq
{@https://lyse.isobeef.org/twtxt.txt>#uj2oxcq} I just noticed a bug in my twtxt client's twt publish form – luckily just before submitting. Why on earth make it most programming languages so easy to misuse their damn date time APIs!? On today's episode we have Python's datetime.datetime.utcnow().replace(second=0, microsecond=0).astimezone().isoformat() which is not what we want, it's actually datetime.datetime.now(datetime.timezone.utc).replace(second=0, microsecond=0).astimezone().isoformat() instead. The former gives us the time in UTC and thus is off by an hour in my case: 2021-01-03T23:30:00+01:00 vs. what I'm really after: 2021-01-04T00:30:00+01:00