# 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/a3e5oyq
Are you able to coax your webserver to add the charset to the content type header? Browsers are having a hard time thinking you are sending latin-1
content-type: text/plain; charset=utf-8
@xuu Is this directed at all pod owners? I've only just started my research, but it looks like I might be able to achieve this with an add_header line in my NGINX proxy pass configuration.
@xuu Is this directed at all pod owners? I've only just started my research, but it looks like I might be able to achieve this with an add_header line in my NGINX proxy pass configuration.
@jlj oh dang the reply didnt add the reply. It was to @hxii because Firefox shows his shruggy like ¯\_(ツ)_/¯
@jlj oh dang the reply didnt add the reply. It was to @hxii because Firefox shows his shruggy like ¯\_(ツ)_/¯
@jlj oh dang the reply didnt add the reply. It was to @hxii because Firefox shows his shruggy like ¯\\_(ツ)_/¯
@jlj oh dang the reply didnt add the reply. It was to @hxii because Firefox shows his shruggy like ¯\\_(ツ)_/¯
@jlj oh dang the reply didnt add the reply. It was to @hxii because Firefox shows his shruggy like ¯\\_(ツ)_/¯
@jlj oh dang the reply didnt add the reply. It was to @hxii because Firefox shows his shruggy like ¯\\_(ツ)_/¯