# 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 7
# self = https://watcher.sour.is/conv/ddivsja
@ocdtrekkie Was looking at fileBrowser and noticed it has an authentication method they call Proxy Authentication -- Can we adopt/borrow this same behaviour for yarnd on Sandstorm? 🤔
@ocdtrekkie Was looking at fileBrowser and noticed it has an authentication method they call Proxy Authentication -- Can we adopt/borrow this same behaviour for yarnd on Sandstorm? 🤔
@prologic That is essentially what Sandstorm already does! We have Sandstorm specific header names, but you can also make the header name you ingest configurable. https://docs.sandstorm.io/en/latest/developing/auth/
The only thing particularly more complicated for Sandstorm is that we don't control the uniqueness of a user's preferred handle, so you do need to user the user-id field for authentication, and then ensure the username is unique inside the app.
Sometimes apps shoehorn the user-id field into like their email or password fields, and then use either username or preferred-handle for the display name depending on the type of app.
Thanks!
Thanks!