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`
…gic (#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.…
matched #nzwfuga score:2.64
Search by:
Search by 1 mentions:
…gic (#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…
matched #baup6sa score:2.09
Search by:
Search by 1 mentions:
…gic (#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 …
matched #2f4helq score:2.73
Search by:
Search by 1 mentions:
…gic (#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 look…
matched #eunq7ca score:2.39
Search by:
Search by 2 mentions: