# 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 17
# self = https://watcher.sour.is/conv/moogcia
@sorenpeter @darch How so? If person A follows B then a relationship can be established.
What can’t be determined reliably is if A stops fetching B’s feed and therefore stops following.
@sorenpeter @darch How so? If person A follows B then a relationship can be established.
What can’t be determined reliably is if A stops fetching B’s feed and therefore stops following.
@sorenpeter @darch How so? If person A follows B then a relationship can be established.\n\nWhat can’t be determined reliably is if A stops fetching B’s feed and therefore stops following.
@prologic yes, I'm aware that a relationship can be established when A (@darch) fetches the feed from B (@sorenpeter). Bu there is nothing anywhere online that can tell you that B follows or fetches A. I don't have a client as such for @sorenpeter except my interface for posting to http://darch.dk/twtxt.txt and a local instance of the original twtxt client on my macbook, that i have not run for over 6 months.
@darch @sorenpeter Oh I see. Yeah well it must have fetched from it at _some_ point 🤣
@darch @sorenpeter Oh I see. Yeah well it must have fetched from it at _some_ point 🤣
@darch @sorenpeter never stored. it happens on demand. It's the equivalent of looking at the UserAgent header when a request comes in for a feed.
@darch @sorenpeter never stored. it happens on demand. It's the equivalent of looking at the UserAgent header when a request comes in for a feed.
