# 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 11
# self = https://watcher.sour.is/conv/3cw3oda
@prologic mkws doesn't support Markdown out of the box, nor does it watch files. Everything is stored in non-hidden directories, is scriptable and highly customizable as opposed to zs. Doesn't have the concept of "plugins", you just write shell code anywhere you prefer.
@adi Actually with zs you can write "programs" or "shell scripts" that are invoked as template functions 😅
@adi Actually with zs you can write "programs" or "shell scripts" that are invoked as template functions 😅
Which will win, which? Dear lord, let me know which!
Michael eats popcorn
@prologic Well regarding what mkws is, just imagine only your extension system. Everything is shell script.
@adi so, if everything is shell script, and just about everything can be done with it, what do we need *zs* or *mkws* for? 🤣
@fastidious Well, regarding mkws is about the few conventions/features: layout file, sitemap generation, css file, cache file, and the shell based templating system. You don't actually _need_ mkws you could write all your website in shell script (@lyse is doing that I believe), but there some subjectively nice small, _optional_, features. Same with zs I guess.
mkws is basically a small set of abstractions I believe are good for generating a static site, with a very powerful templating engine.
@adi You are _right_ about the "subjectivity". I prefer to use zs for now because it "suits my needs" quite well. I just need a basic layout and Markdown. The only "dynamic" part of the build step I use/rely on is calling out to data which renders a nice "Last Modified ..." in the footer of my static sites (_which I have three I maintain at the moment_).
@adi You are _right_ about the "subjectivity". I prefer to use zs for now because it "suits my needs" quite well. I just need a basic layout and Markdown. The only "dynamic" part of the build step I use/rely on is calling out to data which renders a nice "Last Modified ..." in the footer of my static sites (_which I have three I maintain at the moment_).
@prologic I don't believe in "needs", but that's your preference. 😀