# 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 3
# self = https://watcher.sour.is/conv/ptugpdq
@lyse The specification just says:
> Also note that a status may not contain any control characters.
Which is extremely vague, but U+0009 Horizontal Tabulation *is* in the C0 control code block
I'm sure 99% of twtxt parsers don't treat additional tabs any differently. Even Buckket's reference implementation includes additional tabs in the message. Although, in fairness, it doesn't check for *any* for control codes.
Maybe we need a less ambiguous specification documenting how twtxt feeds are being written in the wild. Did you know that the comment convention is not a part of the original spec? I feel like it's used everywhere, even among feeds that don't use any Yarn extensions.
@mckinley Maybe it is about time we just rewrite the spec from the ground up? 🤔
@mckinley Maybe it is about time we just rewrite the spec from the ground up? 🤔