# 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 3
# self = https://watcher.sour.is/conv/tnebpaa
Regarding the ActivityPub conversation, I'm not sure I understand why a bridge wouldn't be the preferred solution. It seems to me a well-done bridge would minimize the downsides while still allowing people to interact with ActivityPub users if they want.
@abucci Yeah originally my idea to support Activity Pub in the first place was an external briding service that yarnd would integrate with (opt-in) and you could spin this bridging service up just like the feeds service (if you car eot run your own).
@abucci Yeah originally my idea to support Activity Pub in the first place was an external briding service that yarnd would integrate with (opt-in) and you could spin this bridging service up just like the feeds service (if you car eot run your own).