# 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/4xx2kfq
eaplmx
twtxt.net
View Thread
Another one, when a resource is available in multiple places, like Gopher, HTTP and Gemini (and IPFS, why not?), are there going to be N registries?

Wild idea, how about using the HTTP response codes https://developer.mozilla.org/en-US/docs/Web/HTTP/Status or from Gemini https://gemini.circumlunar.space/docs/specification.gmi

Like 308/31 for redirections, 410/52 for Gone and such
lyse
lyse.isobeef.org
View Thread
@eaplmx The idea is to only provide mappings for wrong URLs and mark dead ones. So a single database for multiple protocols should do. No need to spin up a dedicated one for a different protocol. If a feed is available over multiple protocols or locations, there's no need to insert any of them, if they work. Unless one wants to rewrite some URLs to some other canonical forms.
lyse
lyse.isobeef.org
View Thread
@eaplmx I forgot to mention that I like the HTTP status codes idea! I need to think about it a bit more, but that sounds very appealing. We just need to watch out that we don't tie it too much to HTTP. I have no clue about Gopher or Gemini.