# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 19
# self = https://watcher.sour.is/conv/qwpzeka
@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 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 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 Why can’t you automate checking your access logs? That’s effectively what twtxt.net’s backend implements — it works quite well IMHO
@deadguy @vain Why can’t you automate checking your access logs? That’s effectively what twtxt.net’s backend implements — it works quite well IMHO
@deadguy @vain Why can’t you automate checking your access logs? That’s effectively what twtxt.net’s backend implements — it works quite well IMHO
@vain @deadguy @prologic 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.
@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 😀
@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 😀
@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 😀
@prologic 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 @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_)
@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_)
@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 I'm sure I will find some time tomorrow or in the next days.
@prologic @lyse @deadguy 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.
@prologic @lyse @deadguy 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.
@prologic @lyse @deadguy 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.
@prologic @lyse @deadguy 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.