# 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 3
# self = https://watcher.sour.is/conv/psdrrxq
It's interesting some of the Gemini detractors point out there is only static content and no way to do anything dynamically... and yet, CGI is still a thing in Gemini if you use a server that supports it. There's literally dynamic search functions and comments sections on some capsules. Very unrefined and still developing, yes, but it's there.
I am not a Gemini detractor, but what can Gemini do that HTTP can’t?
@fastidious Essentially nothing, and I guess it's even designed to do much less. That's kind of the point of it I suppose, and my experience with it is still only a matter of days so far, but the idea is a totally stripped back experience. I guess one could argue one of the 'features' is a complete lack of being tracked, because there's no way to implement cross-site tracking as we know it on Gemini. Anyway it's not meant to replace HTTP, it is its own thing.