# 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 4
# self = https://watcher.sour.is/conv/5l6frtq
We could ask them? But on the counter would bukket or jan6 follow the pure twtxt feeds? Probably not either way... We could use content negotiation as well. text/plain for basic and text/yarn for enhanced.
@xuu That's hilarious that you mention content-negotiation as yarnd does this, and has done for quite some time, though I suspect it achieves nothing 🤣 (it does for AP, Twtxt, etc, though...) -- The original spec didn't even mention content-types or any of the sort, so I very much doubt any older clients (just twtxt the ref client?) even attempts to do this? 🤔
@xuu That's hilarious that you mention content-negotiation as yarnd does this, and has done for quite some time, though I suspect it achieves nothing 🤣 (it does for AP, Twtxt, etc, though...) -- The original spec didn't even mention content-types or any of the sort, so I very much doubt any older clients (just twtxt the ref client?) even attempts to do this? 🤔
@xuu That's hilarious that you mention content-negotiation as yarnd does this, and has done for quite some time, though I suspect it achieves nothing 🤣 (it does for AP, Twtxt, etc, though...) -- The original spec didn't even mention content-types or any of the sort, so I very much doubt any older clients (just twtxt the ref client?) even attempts to do this? 🤔