# 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 1
# self = https://watcher.sour.is/conv/fmrnf3q
{@https://twtxt.net/user/prologic/twtxt.txt>#36nfz6q} @deadguy (#xfsjdlq) Yes it's all possible. We haven't built this support yet, but it is something I want to do! Do you have any experience writing Go? If so we would love the contributions! The way I was thinking of this working is to extend the command-line client we have today (twt) into both a traditional Twtxt client that mutates a local twtxt.txt file but also knows how to connect to a Twt.social pod. The expected workflow would be an (_optionaly_) occasional twt login and twt sync. What do you think?