# 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 15
# self = https://watcher.sour.is/conv/mnpnvda
I would love to see a world where ones twtxt feed is defined by webfinger. So @xuu@txt.sour.is => https://text.sour.is/user/xuu/twtxt.txt
Then my identity can exist independent of the feed location. And I can host multiple protocol types for my feed. Ie. http/gopher/Gemini/irc DCC/etc
@xuu That's not a bad idea, actually.
@xuu That's an interesting idea. Twt hashes still need a canonical URL to work, though.
@xuu This is already supported by Yarn.
Perhaps we just need to formalise l it? 🤔
@xuu This is already supported by Yarn.
Perhaps we just need to formalise l it? 🤔
@xuu This is already supported by Yarn.
Perhaps we just need to formalise l it? 🤔
@prologic Yes please, my default way of storing Twtxt usernames right now is as a URL, but I think Webfinger would be nice as well
Then let's spec this up 👌 I fully support this 🤗
Then let's spec this up 👌 I fully support this 🤗
Then let's spec this up 👌 I fully support this 🤗