@gareppa @gareppa (#7mcr2ea) Hey, same to you! Which of your feeds is the real deal? The one on twtxt.net or tilde.club? It also seems that your User-Agent HTTP header from tidle.club is broken, there's a superfluous "public_html/" in the path. ;-)

@vain @deadguy @prologic (#qwpzeka) I'm currently in the process to come up with something automated, too. At the moment I manually check my Nginx access log with `cut -d ' ' -f 12- ~/www/logs/twtxt.log|sort|uniq -c` It works for now, but it's certainly not good enough. I definitely want to filter out search engine and other unusable UAs, fold software versions (twtxt.net with its git hashes comes to mind ;-)) and also check the result against my subscribed feeds, to quickly discover new subscribers.

(#qwpzeka) @lyse Yeap sounds like a good idea to me. Why don't you also take advantage of the Twtxt `User-Agent` format too and parse that out and filter against it? That way you can cut down on the noise. In the future you _may_ also want to extend this to support the format used by Twtxt.net when you have more than one follower from a pod 😀

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`

@prologic (#qwpzeka) Exactly, that's what I probably end up doing. But first I have to write up the spec on this extension, I reckon. :-D Yesterday I came across that issue and pull request, both you and @vain had discussed back then.

@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.

(#qwpzeka) @lyse @vain Yeah it would be nice to document an extension to the Twtxt User Agent for effectively what multi-user clients are (_which his what twtxt.net really is_)

@prologic (#qwpzeka) I'm sure I will find some time tomorrow or in the next days.

@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 👌