# 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 5
# self = https://watcher.sour.is/conv/dt4rbaq
@prologic ohh I see. I think the difference between the two hadn't quite clicked.
So in that case why wouldn't it be possible to have an ActivityPub bridge that forced yarn semantics (so to speak)? If someone sent you a reply via ActivityPub you wouldn't see it on yarn unless you followed their feed?
@abucci That was the original plan actually, but I started out this way "because it was easier" at the time. But now that I know more about how it works in general, I'm thinking it might be better to revere tract and go back to the drawing board.
@abucci That was the original plan actually, but I started out this way "because it was easier" at the time. But now that I know more about how it works in general, I'm thinking it might be better to revere tract and go back to the drawing board.
@abucci That was the original plan actually, but I started out this way "because it was easier" at the time. But now that I know more about how it works in general, I'm thinking it might be better to revere tract and go back to the drawing board.
@abucci That was the original plan actually, but I started out this way "because it was easier" at the time. But now that I know more about how it works in general, I'm thinking it might be better to revere tract and go back to the drawing board.