# 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 10
# self = https://watcher.sour.is/conv/l6sm5ba
@lyse but he can write to ~/duriny/, and keep an index.html there with the meta tags. As I see it, it should work just fine. I shall test it later this afternoon, as I have accounts on a few tildes around.
@fastidious Actually my https://pronoun.is/they no biggie :)
@~duriny my apologies for assuming. I normally look at the person's profile (on Yarn) for a description. Some like to list their pronoun there, which makes it easier. Now, why I assumed Duriny was a he, and not a she—or a they—boggles my mind now. Truly, my apologies.
No worries mate, I've added a # pronouns = field to my twtxt.txt, should have thought to do that earlier
If you really care about it, you should probably put it in the `description`, @~duriny, as it probably won't get picked up by yarnd otherwise, I reckon. I'm not sure whether other clients use the pronouns field, though. And one thing to be aware of is that not all clients support these metadata fields or even metadata fields at all.
@lyse I was thinking about the same. I am one of the few who peeks at the raw feed, but most people using Yarn will not. Now, the description people will for sure see.
Thanks @lyse, will do :)
@fastidious would it be a good idea to add support for the pronouns field to yarn?
@~duriny that is a question that's worth debating. Open an issue for it, and I will tag it as discussion to see what people think. Being on the minimalistic side, I would say let us use the description for it, without the need to add another meta/field to the feed, but I am only one. I think opening it for discussion is worth it.
@fastidious I usually just look at the raw feed before deciding whether I subscribe to a feed or not. Regarding metadata I fully support the simplicity argumentation. description seems to be enough for me (now on a side note tt doesn't even care about metadata at the moment at all, 'cause the twtxt client downloads and processes the feeds, tt is still just a viewer, but it will change).