# 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 1
# self = https://watcher.sour.is/conv/j5uigta
i keep debating this in my head. i reckon the comrade's display device should be modular anyway, the display buffer is just that. doesn't matter if there's a TFT or an e(ink|paper) display on the other side. multiplexing uxn displays would be cool, but that would mean adding a display buffer cache for every instance and i don't know if i want to have that much memory dedicated to swapping displays. i'm on board with using uxn as a common runtime, but FRAM modules have six pins and top out at 256k (afaik). i only have 88 pins to work with so i'll have to place some hard limits on how many display devices the runtime allows.