# 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 5
# self = https://watcher.sour.is/conv/budayha
@mckinley That’s 100% correct and the dev.twtxt.net just needs to be redeployed today which I’ll do today 👌
@mckinley That’s 100% correct and the dev.twtxt.net just needs to be redeployed today which I’ll do today 👌
would I make sense to move stuff from dev.twtxt.net to dev.yarn.social?
@darch I _thought_ about that for a brief moment, but I _realized_ that most of the content we've created at dev.twtxt.net _actually_ centers around very specific content related to the twtxt spec itself and the extensions we've created atop and around it without breaking existing clients. So I'm not sure 🤔 -- I _think_ Yarn.social development _has_ to be a bit different anyway, how to build the software, the UI/UX, the API, the various tools and services we've built to support the larger platform, etc...
@darch I _thought_ about that for a brief moment, but I _realized_ that most of the content we've created at dev.twtxt.net _actually_ centers around very specific content related to the twtxt spec itself and the extensions we've created atop and around it without breaking existing clients. So I'm not sure 🤔 -- I _think_ Yarn.social development _has_ to be a bit different anyway, how to build the software, the UI/UX, the API, the various tools and services we've built to support the larger platform, etc...