# 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 6
# self = https://watcher.sour.is/conv/hvygjbq
The recommended way to distribute dependencies with your mkws websites is to bundle them as static binaries so you don't have to run any package manager on the server side either. So, if your website uses smu, distribute a statically compiled smu in your website's ./bin directory. The recommended way of doing this is to do a make install PREFIX=/path/to/mkws/website/root. Make sure the -static flag is set. That way you will also get the man pages installed in the ./share/man directory.
@adi (#hvygjbq) @eldersnake Check this out ^ Of course you can install the dependencies on the server also but it's not always viable as there is no package.json or requirements.txt or something similar.
@adi (#hvygjbq) @eldersnake Check this out ^ Of course you can install the dependencies on the server also but it's not always viable as there is no package.json or requirements.txt or something similar.
@eldersnake Depends on what you understand by Suckless.
@eldersnake Depends on what you understand by Suckless.