# 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/zltzria
@andros, I am getting:


Feed was redirected: https://twtxt.andros.dev -> https://twtxt.andros.dev/



Each time my client fetches your feed. It just doesn't make any sense to me. Wouldn't be both, pretty much, be the same (I noticed the /, yes)?
@andros, I am getting:


Feed was redirected: https://twtxt.andros.dev -> https://twtxt.andros.dev/



Each time my client fetches your feed. It just doesn't make any sense to me. Wouldn't be both, pretty much, be the same (I noticed the /, yes)?
working on my bookmarks tool, I found out that http(s)://domain.tls is not a valid resource, but http(s)://domain.tls/ is, as you can see here: https://stackoverflow.com/a/2581423

I suppose that internally the wget/curl or whatever client you are using is redirecting it?
also @Andros, I see that if I open that URL on my browser, I see weird characters in the .txt file:
description = 🏗
Perhaps your nginx server is missing a Content-Type: text/html; charset=utf-8 header?
https://serverfault.com/a/975289

In timeline it looks OK however, I think it's relying on
> The file must be encoded with UTF-8
of the original spec:
https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html
@eapl.me Can you check now, please?
@eapl.me Can you check now, please?
looks good now!
description = 🏗 Full-Stack developer (Mainly Python) ✍ Writer[...]