BTW, researching on that I found that @prologic was working on the following #supported-user-agent-formats">https://git.mills.io/yarnsocial/useragent#supported-user-agent-formats

I wasn't aware of a few `User-Agent Formats`.

And I'm checking that `timeline` is not sending those headers. I should push a change on that soon.

@eapl.mx Yes, the idea is to add User Agent support to #Timeline.
Right now it just adds every request to a growing log file, but I have also been working on a way to analyse it, so it only saves the time of the latest request.
I'm not sure how to make it part of timeline itself, since it requeses that you redirect/rewrite from `twtAgent.php` to the acctual `twtxt.txt`
Help with making Timeline send proper User Agents to others would be much appreciated:)

I sent a few local tests, could you help me check if you see `https://eapl.mx/twtxt.txt` in your log file?

If you want more eyes on the agent, you can tell tell me, as I was thinking on something similar to catch those 'following requests'.

My `twtAgent.php` was turned off, so try again now. I have uploaded the code to: https://github.com/sorenpeter/twtAgent

did it work? I tried loading the file from /twtxt.txt, /twtAgent.php and /twtAgent2.php

Also reading the code, I see it creates two files, but I'm not sure which you are using now:
http://darch.dk/twtAgent.log <- 403 Forbidden
and
http://darch.dk/twtAgent.csv <- Not found here

Yes it work: `2024-12-01T19:38:35Z twtxt/1.2.3 (+https://eapl.mx/twtxt.txt; @eapl)` :D

The .log is just a simple append each request. The idea with the .cvs is to have it tally up how many request there have been from each client as a way to avoid having the log file grow too big. And that you can open the .cvs as a spreadsheet and have an easy overview and filtering options.

Access to those files are closed to the public.

test post EDIT