@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
matched #nfgcqjq score:12.2
Search by:
Search by 2 mentions:
@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.
matched #lyrb36a score:12.2
Search by:
Search by 3 mentions:
(#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 😀
matched #shnxyda score:12.2
Search by:
Search by 1 mentions:
@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.
matched #woa6l2q score:12.2
Search by:
Search by 2 mentions:
(#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_)
matched #tfku7sa score:12.2
Search by:
Search by 2 mentions:
@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.
matched #jylu4hq score:12.2
Search by:
Search by 3 mentions: