# 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/ffzq53q
@movq Oooooohhhhhh, I see. Hmmmm.
To answer your question: Ideally, you would have replied directly to my reply. :-) The flat conversation model always felt unnatural to me. I just yielded to the community's way of doing it.
@lyse there are times that it works out to reply to the "flat" conversation, if it fully relates, or the participants are few, or if the strict topic is kept. When there are too many people, or too many topics being spit out, then forking constantly is the way to go. I am a strong proponent of forking. It's like telling the rest, "you debate that there, I will take this one aside".