# 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 6
# self = https://watcher.sour.is/conv/7xnsrsa
One of the frustrating parts of using twtxt for conversations is the URLs are, well... ugly. Anyone (like y'all yarn folks) looked at using webfinger for translating user@domain accounts to URLs?
One of the frustrating parts of using twtxt for conversations is the URLs are, well... ugly. Anyone (like y'all yarn folks) looked at using webfinger for translating user@domain accounts to URLs?
@anth Yes actually, we have been looking at that recently. Once upon a time I came up with my own hacky (indieweb / git / go inspired) way of doing something similar, but I _think_ yarnd instances could have builtin support for WebFinger pretty easily (server-side and client lookups and expansion).
@anth Yes actually, we have been looking at that recently. Once upon a time I came up with my own hacky (indieweb / git / go inspired) way of doing something similar, but I _think_ yarnd instances could have builtin support for WebFinger pretty easily (server-side and client lookups and expansion).
@anth Yes actually, we have been looking at that recently. Once upon a time I came up with my own hacky (indieweb / git / go inspired) way of doing something similar, but I _think_ yarnd instances could have builtin support for WebFinger pretty easily (server-side and client lookups and expansion).
@anth Yes actually, we have been looking at that recently. Once upon a time I came up with my own hacky (indieweb / git / go inspired) way of doing something similar, but I _think_ yarnd instances could have builtin support for WebFinger pretty easily (server-side and client lookups and expansion).