# 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 14
# self = https://watcher.sour.is/conv/qr2zwmq
@lyse @prologic Too tired to check, but: Is non-ASCII allowed in HTTP referers?
@lyse @prologic Too tired to check, but: Is non-ASCII allowed in HTTP referers?
@lyse @prologic Too tired to check, but: Is non-ASCII allowed in HTTP referers?
Errr. User agent, of course.
Errr. User agent, of course.
Errr. User agent, of course.
@movq Good question, I didn't think of the User-Agent header! So according to this answer it's a fragile thing, we probably need to implement MIME encoding in the clients ourselves.
@movq To complete, the Referer isn't a problem I'd say, since it's a URL and Unicode can be URL-encoded.
@lyse
> we probably need to implement encoding
Not sure if want. 😕
@lyse
> we probably need to implement encoding
Not sure if want. 😕
@lyse
> we probably need to implement encoding
Not sure if want. 😕
@movq No, my enthusiasm is limited. Right now I think we should not go down the Unicode nickname rabbit hole. I cannot be done in a real backwards-compatible fashion as far as I can tell.