# 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 4
# self = https://watcher.sour.is/conv/zf7oiza
movq
www.uninformativ.de
View Thread
https://alex.party/posts/2025-05-05-the-future-of-web-development-is-ai-get-on-or-get-left-behind/
kat
yarn.girlonthemoon.xyz
View Thread
@movq I LOVE THIS POST LOL
kat
yarn.girlonthemoon.xyz
View Thread
@movq I LOVE THIS POST LOL
movq
www.uninformativ.de
View Thread
And on a similar note, cross-post from Mastodon:

What I love about HTML and HTTP is that it *can* degrade rather gracefully on old browsers.

My website isn’t *spectacular* but I don’t think it looks *horrible*, either. And it’s still usable just fine all the way down to WfW 3.11:

* Some blog post in various browsers
* Git repo viewer (stagit)
* Older photos of WfW 3.11

It’s not *perfect*, but it’s *usable*. And that makes me happy. Almost 30 years of compatibilty.

The biggest sacrifice is probably that I don’t enforce TLS and that HTTP 1.0 has no Host: header, so no vhosts (or rather, everything must come from the default vhost). (Yes, some old browsers send Host:, even though they predate HTTP 1.1. Netscape does, but not IBM WebExplorer, for example.)

(On the other hand, it might completely suck on modern mobile devices. Dunno, I barely use those. 🤪)*