[…] my server logs it shows that your site pulled in the useragent as https://eapl.me/twtxt/?url=https%3A//neotxt.dk/user/darch/twtxt.txt with bytesypider from bytedance?
Didn’t know of bytesypider and bytedance, I assume those are bots, although I no idea why they are pointing to that address to your site
https://wordpress.org/support/topic/psa-bytedance-and-bytespider-bots-recommend-blocking/
twtxt-php isn’t sending User-Agent headers as it’s in the original spec:
https://twtxt.readthedocs.io/en/latest/user/discoverability.html
Or the discussion there:
https://github.com/buckket/twtxt/issues/109
I think it could be easy to implement 🤔
Since relying on HTTP logs could be inconvenient on some servers, there were ideas of using WebMention or some HTTP endpoint to inform who’s following your URL (like on Gemini Antenna).
From what I’ve read, timeline and yarn has experimental support for Webmention. Could @prologic@twtxt.net or @darch@neotxt.dk share some insights on that?