# 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 10
# self = https://watcher.sour.is/conv/65k6uvq
@movq But it makes sense, right? I spend way too much time trying to figure out who replied to whom. I treat twts replies as emails, pretty much.
@quark It does make sense, yeah. (I got used to reading flat conversations when the microblog that we used at work no longer supported threading. But I remember, back then, I was pretty pissed. 🤣)
@quark It does make sense, yeah. (I got used to reading flat conversations when the microblog that we used at work no longer supported threading. But I remember, back then, I was pretty pissed. 🤣)
@quark It does make sense, yeah. (I got used to reading flat conversations when the microblog that we used at work no longer supported threading. But I remember, back then, I was pretty pissed. 🤣)
@movq At least both our clients handle these trees really well. ;-)
Well I normally use Goryon most of the time but in either case Web or Mobile it’s handled just as nicely as tt or jenny IHMO. Neither yarnd nor Goryon display trees though ☺️
Well I normally use Goryon most of the time but in either case Web or Mobile it’s handled just as nicely as tt or jenny IHMO. Neither yarnd nor Goryon display trees though ☺️