# 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 13
# self = https://watcher.sour.is/conv/mgpqjra
@screem consider yourself not minded, LOL. It would have been easier and, perhaps, more everlasting, to put the screenshots on git as well. They can be referenced from the wiki, and it would be all self-contained. Right now you have documentation hot linking images on your pod. For me that's a no-no.
Just commit them to /docs ๐
Just commit them to /docs ๐
@david I'll change that tomorrow. For now, I rest ๐ด
@screem I'd add all these in text form rather than images. This has three advantages: It's less bytes, searchable and can be copied.
@lyse Great point! Never really considered the pros to that approach and really does seem like the best approach imo. I'll get onto that tomorrow afternoon ๐ Appreciate the feedback
I've updated the images to just be a bash code block or table now ๐
@screem Very nice! Much cooler this way. I even found three more reasons: It can be versioned much easier than another remote file, you also save on additional HTTP requests in that particular case and editing works with every editor. The last and fourth one I sadly forgot in the meantime.
For the curiousโor the lostโwe are talking about a document @screem created on the Yarn repository wiki, about running a Yarn pod on Docker with Apache2.
@lyse Glad it has more functionality! I'll probably stray from screenshots in technical documentation from now on!
