# 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 22
# self = https://watcher.sour.is/conv/4u4kayq
@prologic commented there, but also here. I think the proposal includes things I would have wanted, and some I would not have thought of. It is pretty good!
@fastidious Cool! π Also this is a significant body of work π
Q: What should the internal event steam/feed be called? π€ I kind of want to get away from calling it @twtxt
@fastidious Cool! π Also this is a significant body of work π
Q: What should the internal event steam/feed be called? π€ I kind of want to get away from calling it @twtxt
@prologic why don't we call it "Jeeves" or "Jarvis"?
βHow did you hear of me?β β βBob told me.β
βHow did you find such an interesting feed to follow?β β βThrough Bob!β
What if it were customizable on a per user basis? With a pod level default? π€
What if it were customizable on a per user basis? With a pod level default? π€
@prologic
> What if it were customizable on a per user basis? With a pod level default?
Now you are cooking!
@fastidious Jarvis is my bro, so that'd be confusing. π
@jlj called it "brother" then
@meff Good thinking but Iβm still thinking about how this will even work at all yet π€ I have some ideas but trying to avoid having to change the Twtxt spec yet again π€£
@meff Good thinking but Iβm still thinking about how this will even work at all yet π€ I have some ideas but trying to avoid having to change the Twtxt spec yet again π€£