# 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 23 # self = https://watcher.sour.is/conv/yrhfw7q
#! DOCTYPE = twtxt (https://twtxt.readthedocs.io) with extension for multi-line and conversation treading from Yarn.social (https://dev.twtxt.net)dev.yarn.social, docs.yarn.social or similar instead of dev.twtxt.net to make it less confusing.
# doctype = whatever? Also, which problem does this solve? What would clients do differently? And humans just could look at the comment or URL and see that this feed makes use of extensions – if they care. Twtxt purists would certainly hate such a new thing, too, I don't think it helps them in any way. So I don't see the use case for that. Can you please elaborate, @darch, what you had in mind?
# Learn more about twtxt at: https://github.com/buckket/twtxt
# This feed makes use of some extensions: https://dev.twtxt.net/
# type = ... and # exts = ...? 🤔
# type = ... and # exts = ...? 🤔
# type = ... and # exts = ...? 🤔