# 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 23
# self = https://watcher.sour.is/conv/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
@lyse Is that formatting the date/time as RFC3339? (_been a while since I've used Python_) π€ -- It _should_ / _needs_ to be in RFC3339.
@lyse Is that formatting the date/time as RFC3339? (_been a while since I've used Python_) π€ -- It _should_ / _needs_ to be in RFC3339.
@lyse Is that formatting the date/time as RFC3339? (_been a while since I've used Python_) π€ -- It _should_ / _needs_ to be in RFC3339.
@prologic Absolutely correct, this format is actually both ISO 8601 as well as RFC 3339, where ISO 8601 is a superset of RFC 3339, making dashes and colons optional among other things. `datetime.isoformat()` produces the ISO 8601 formatted timestamp, which happens to be RFC 3339-compliant, too.
@lyse Cool! Should work fine then π
@lyse Cool! Should work fine then π
@lyse Cool! Should work fine then π
@lyse Is this your own client you're implementing and using or an existing client?
@lyse Is this your own client you're implementing and using or an existing client?
@lyse Is this your own client you're implementing and using or an existing client?
@prologic I'm using my own terrible mess over here, there's also a small screenshot (not sure whether you can make out anything). It actually started out as something completely different. I just wanted to fool around with Urwid, a Python text user interface library. But you know how things end up. ;-) At the moment I rely on the official twtxt CLI for fetching, caching and following, but some day I'm gonna integrate it into tt for sure. Hopefully sooner rather than later. This client is currently in a really horrible state and not very usable by others (hardcoded paths and crap like this). Finally going to bed now, see you in a couple of hours, g'night!
@prologic No offence, to me it seems this client is abandoned, there are three PRs untouched for months or even years, which fix actual crashes of the client. When I discovered the crashes on my own and fixed them, I wanted to send a PR, but then realized that they had all been already addressed by some folks, but nothing happend. So I then didn't bother any further.
@prologic On a side note, is it just an operator error or is there actually a bug in one of your clients? You replied to the broken URL https://lyse.isobeef.orgd/user/lyse/twtxt.txt, which looks like a twtxt.net instance, but there's also a "d" appended to the top level domain. I've seen the exact same pattern happening three days ago with @vain in this twt: https://www.uninformativ.ded/user/vain/twtxt.txt
@lyse Yeah I know. π₯ Itβs sad that @buckket no longer maintains twtxt the spec or his reference client π₯
@lyse Yeah I know. π₯ Itβs sad that @buckket no longer maintains twtxt the spec or his reference client π₯
@lyse Yeah I know. π₯ Itβs sad that @buckket no longer maintains twtxt the spec or his reference client π₯
@vain @lyse Oooh thatβs interesting ! π³ Iβm not sure to be honest π€
@vain @lyse Oooh thatβs interesting ! π³ Iβm not sure to be honest π€
@vain @lyse Oooh thatβs interesting ! π³ Iβm not sure to be honest π€