@deadguy Why do you think it’s not a good idea? 🤔 twtxt feels a bit too “one-way” at times, since apparently many people don’t check their access.log and don’t know you’re following them / mentioning them. I originally thought this was an advantage, less noise. Dunno, maybe this is just the coronavirus isolation speaking through me. 🥴

@deadguy @vain (#qwpzeka) Why can’t you automate checking your access logs? That’s effectively what twtxt.net’s backend implements — it works quite well IMHO

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

…#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 no…

…gic (#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 @v…

(#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 @lyse @deadguy (#qwpzeka) Oh, I do have it automated. :) Just feels like other people don’t do it. No idea, maybe it’s just because this community is so tiny.