@lyse (#uj2oxcq) Is that formatting the date/time as `RFC3339`? (_been a while since I've used Python_) 🤔 -- It _should_ / _needs_ to be in RFC3339.

@prologic (#uj2oxcq) 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.

(#uj2oxcq) @lyse Cool! Should work fine then 👌

(#uj2oxcq) @lyse Is this your own client you're implementing and using or an existing client?

@prologic (#uj2oxcq) 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!

@lyse (#uj2oxcq) Ahhh. Yes I remember now. We should make a PR upstream to buckket/twtxt and add some of the extensions documented at dev.twtxt.net

@prologic (#uj2oxcq) 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 (#uj2oxcq) 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 (#uj2oxcq) Yeah I know. 😥 It’s sad that @buckket no longer maintains twtxt the spec or his reference client 😥

@vain @lyse (#uj2oxcq) Oooh that’s interesting ! 😳 I’m not sure to be honest 🤔