# 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/cw2d3lq
@prologic I'm glad you found my idea compelling. I agree that the broker and client specifications shouldn't be lumped together. I also think there should be a clear separation between client-to-server and server-to-server connections. The distinction between sending a message (POST http://montague.example/api/base/v1/post) and delivering a message (POST http://capulet.example/api/base/v1/inbox) should absolutely be enforced by the specification. I didn't see that last night, but it became clear after thinking about it.