# 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 8
# self = https://watcher.sour.is/conv/orerkha
@jason Then it is supportted and you've used it 🥳
@jason Then it is supportted and you've used it 🥳
@prologic I think now I know what forked threads are and figured out how to use them but i don't really know
@jason Is just the way threading work. Essentially conversations can be forked as side topics naturally occur. Conversations or Yarns form a tree like structure of Twts and Twt Hashes distributed over clients
@jason Is just the way threading work. Essentially conversations can be forked as side topics naturally occur. Conversations or Yarns form a tree like structure of Twts and Twt Hashes distributed over clients
Sinxe Twts are content addressable (Twt Hash) this works really well 👌
Sinxe Twts are content addressable (Twt Hash) this works really well 👌