# 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/z66scqa
What about a meta header for setting charset?
I myself stumbled upon .txt files not being delivered with charset: utf-8 by default.
I had to set/modify .htaccess to correct that.
It would have been easier if there had been a charset header entry "overwriting" what http server is delivering.
What do you think?
@stackeffect isn't that something up to the web server to do? How can we overwrite headers, when serving a plain text file? I mean, Yarn could do it, yes, but for anyone else hosting their own twtxt.txt (or whatever they want to name it), how?
@stackeffect I believe Yarn assumes utf-8 anyway which is why we don’t see encoding issues
@stackeffect I believe Yarn assumes utf-8 anyway which is why we don’t see encoding issues
@lyse We should add this to a list of things to include in a “whole” v2 spec
@lyse We should add this to a list of things to include in a “whole” v2 spec
@prologic What do you want to consider in v2? Support for different encodings? So people can now also chose EBCDIC? ]:->
@lyse No lol I just mean a complete v2 spec 🤣 A rewrite 😆
@lyse No lol I just mean a complete v2 spec 🤣 A rewrite 😆
@prologic
> I believe Yarn assumes utf-8 anyway which is why we don’t see encoding issues
Are you sure? I think in #kj2c5oa @quark mentioned exactly that problem. My logs say "jenny/latest" was fetching my twtxt for quark.
All I did to fix this was to adding AddCharset utf-8 .txt to .htaccess. Especially I did not change encoding of stackeffect.txt.
@prologic \n\n> I believe Yarn assumes utf-8 anyway which is why we don’t see encoding issues\n\nAre you sure? I think in #kj2c5oa @quark mentioned exactly that problem. My logs say "jenny/latest" was fetching my twtxt for quark.\n\nAll I did to fix this was to adding AddCharset utf-8 .txt to .htaccess. Especially I did not change encoding of stackeffect.txt.
@stackeffect i’m fairly sure yes! The parser uses runes to parse the content effectively treating the content as utf-8
@stackeffect i’m fairly sure yes! The parser uses runes to parse the content effectively treating the content as utf-8