# 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 2
# self = https://watcher.sour.is/conv/o67gqfa
Double congrats, @thecanine! \o/

I'm not a fan of the gemtext limits. This being only a single page (which probably doesn't get updated a whole lot), the efforts of having two dedicates files are not all that big, or so I'd at least naively imagine.

I always recommend checking the W3C validator results, even though I'm very guilty of not doing that myself. It just doesn't occur to me in the heat of the moment. I reckon if I were writing HTML on a more regular basis, I would pick up on making that a real habit. Anyway, your HTML being generated, you probably can't address the findings, though. So, might not be even worth the time heading over to the validator.

From a privacy point of view, personally, I would definitely host the CSS myself. Other than that, nice link collection. :-)
@lyse It’s possible to run the validator locally (my blog generator scripts do that):

https://validator.w3.org/nu/about.html

That way you don’t forget. 🥳