# 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 20
# self = https://watcher.sour.is/conv/s26j2ca
@prologic
> Technically though this limitation doesn’t need to exist, but I’m not sure we should really change it either?

It would make Yarn a bit more unique. I, for one, would love to use my real name, Jürgen. 😁
@fastidious In that case then, let's explore this...

Some questions:

- Will most file systems handle this okay as the feed's filename and avatar filenames?
- Is this supported in the URI
@fastidious In that case then, let's explore this...

Some questions:

- Will most file systems handle this okay as the feed's filename and avatar filenames?
- Is this supported in the URI spec so URLs for feeds will still work?
- _anything else I might be missing?_ 🤔

Someone willing to muck with the regex and give this a go? 😂_
@fastidious In that case then, let's explore this...

Some questions:

- Will most file systems handle this okay as the feed's filename and avatar filenames?
- Is this supported in the URI spec so URLs for feeds will still work?
- _anything else I might be missing?_ 🤔

Someone willing to muck with the regex and give this a go? 😂_
@prologic I will test the questions. I am sure the regex is out there already, but maybe @lyse and/or @movq can help on that?
@fastidious So the regex just needs to be updated to support Unicode and to have the same set of rules, namely:

- Must start with a letter -- Even if that letter is in another language
- Must only contain letters, numbers, underscores and dashes
- Must be no longer than 15 characters long

I'm sure we can make this happen and support Username/Feed names in other languages! 😅 👌
@fastidious So the regex just needs to be updated to support Unicode and to have the same set of rules, namely:

- Must start with a letter -- Even if that letter is in another language
- M
@fastidious So the regex just needs to be updated to support Unicode and to have the same set of rules, namely:

- Must start with a letter -- Even if that letter is in another language
- Must only contain letters, numbers, underscores and dashes
- Must be no longer than 15 characters long

I'm sure we can make this happen and support Username/Feed names in other languages! 😅 👌
@prologic Funny how we failed to specify this in the metadata extension. As the whole file is encoded as UTF-8, it’s technically legal to use any UTF-8 string for nick, eh? 🥴

Might break stuff in jenny/mutt, but I haven’t tested it.
@prologic Funny how we failed to specify this in the metadata extension. As the whole file is encoded as UTF-8, it’s technically legal to use any UTF-8 string for nick, eh? 🥴

Might break stuff in jenny/mutt, but I haven’t tested it.
@prologic Funny how we failed to specify this in the metadata extension. As the whole file is encoded as UTF-8, it’s technically legal to use any UTF-8 string for nick, eh? 🥴

Might break stuff in jenny/mutt, but I haven’t tested it.
@movq
> Might break stuff in jenny/mutt, but I haven’t tested it.

Yup, RE_NICK_INVALID.
@fastidious @prologic At first I thought, that the original Twtxt Specification limited the nicks to be ASCII-only, but I was wrong. I couldn't find anything in that regard. The reference implementation also allows it:

$ twtxt follow äöüß https://example.com
✓ You’re now following äöüß.
@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?
@movq Yeah we should try to support this 😁
@movq Yeah we should try to support this 😁
@lyse Cool! 👌
@lyse Cool! 👌