# 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 2
# self = https://watcher.sour.is/conv/7aasi2a
thinking about a building something in the realm of @gesture that could work alongside @gest. The core principle of gest is line construction using breakpoints and an external clock. This new system, which I think I will call sloop, is more about making lines using slope. It would work by sending it messages: go from here, to there, in some amount of time, and use an external clock. If it reaches there, you have arrived. If a new message arrives before you get there, you are already here, now you have a new there. I think this approach would lend itself well to more open-ended kinds of gestures. #halfbakedideas
thinking about a building something in the realm of @gesture that could work alongside @gest. The core principle of gest is line construction using breakpoints and an external clock. This new system, which I think I will call sloop, is more about making lines using slope. It would work by sending it messages: go from here, to there, in some amount of time, and use an external clock. If it reaches there, you have arrived. If a new message arrives before you get there, you are already here, now you have a new there. I think this approach would lend itself well to more open-ended kinds of gestures. #halfbakedideas