# 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 6
# self = https://watcher.sour.is/conv/ir4qjla
@prologic I see: I was speaking in the end user's perspective tho, I suppose those concerns only really affect the pod owner? And, if that is the case, giving a pod owner the ability to toggle AP integration on/off us probably good enough to mitigate those concerns?
@marado Yes its' not just the "User Experience" that has to be considered when adding any new features IMO. As discussed in this thread with @abucci there are legitimate concerns because of the "push" model that is Activity Pub.
@marado Yes its' not just the "User Experience" that has to be considered when adding any new features IMO. As discussed in this thread with @abucci there are legitimate concerns because of the "push" model that is Activity Pub.
@marado Yes its' not just the "User Experience" that has to be considered when adding any new features IMO. As discussed in this thread with @abucci there are legitimate concerns because of the "push" model that is Activity Pub.
@marado Yes its' not just the "User Experience" that has to be considered when adding any new features IMO. As discussed in this thread with @abucci there are legitimate concerns because of the "push" model that is Activity Pub.