# 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 9
# self = https://watcher.sour.is/conv/da7imfq
@quark Because “Reply” also fills in mentions. “Fork” does not. Slightly different actions IHMO ☺️
@quark Because “Reply” also fills in mentions. “Fork” does not. Slightly different actions IHMO ☺️
@prologic Make it fill in mentions? Problem solved. 😊
@quark Hah! 😆 I don’t like it 🤣 You then have very few ways to keep adding to a conversation chain, only forks of forks of forks 😂
@quark Hah! 😆 I don’t like it 🤣 You then have very few ways to keep adding to a conversation chain, only forks of forks of forks 😂
See this previous chain got forked! 😁
See this previous chain got forked! 😁
@prologic @quark The problem remains that reading a "flat" conversation is confusing to the point of being messy. One has to figure out who is replying to whom, and even when found, it is not all clear. Hitting reply to a message in a conversation (not the "root" one) does nothing to signify to whom I am replying.
