# 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 5
# self = https://watcher.sour.is/conv/ee7jksq
@marado well, I find that's a problem of leaving that open. Using should vs must. Leaves that to different interpretations.
https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html
>A status should consist of up to 140 characters, longer status updates are technically possible but discouraged. twtxt will warn the user if a newly composed status update exceeds this limit, and it will also shorten incoming status updates by default.
@eaplmx Sadly the simple fact here is; We can debate this part of the spec until the cows come home (_a silly English/Australian expression_). There is just no way to agree on this at all. IMO it should be removed from the spec entirely. yarnd (as one client) for example just makes this configurable, ful-stop, with a reasonable default value that has been discussed and widely agreed upon by the community at least twice now.
@eaplmx Sadly the simple fact here is; We can debate this part of the spec until the cows come home (_a silly English/Australian expression_). There is just no way to agree on this at all. IMO it should be removed from the spec entirely. yarnd (as one client) for example just makes this configurable, ful-stop, with a reasonable default value that has been discussed and widely agreed upon by the community at least twice now.
@eaplmx Sadly the simple fact here is; We can debate this part of the spec until the cows come home (_a silly English/Australian expression_). There is just no way to agree on this at all. IMO it should be removed from the spec entirely. yarnd (as one client) for example just makes this configurable, ful-stop, with a reasonable default value that has been discussed and widely agreed upon by the community at least twice now.
@eaplmx Sadly the simple fact here is; We can debate this part of the spec until the cows come home (_a silly English/Australian expression_). There is just no way to agree on this at all. IMO it should be removed from the spec entirely. yarnd (as one client) for example just makes this configurable, ful-stop, with a reasonable default value that has been discussed and widely agreed upon by the community at least twice now.