# 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 9
# self = https://watcher.sour.is/conv/qdiqjyq
#randomIdeaOfTheDay
Instead of limiting twts by number of characters, do it by num of words, 42 for instance. optionally 69
@eaplmx German twts will win. :-D When looking at the number of bytes.
@eaplmx I don't think we need to plac arbitrary limits at all! In fact, the only reason that Yarn.social pods still have a limited at all is to prevent abuse from bad actors.
@eaplmx I don't think we need to plac arbitrary limits at all! In fact, the only reason that Yarn.social pods still have a limited at all is to prevent abuse from bad actors.
@prologic Well, I missed context. I'm talking about soft limits (based on Twitter obviously) recommended by the spec and that a few CLI follow
> 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.
This random idea was inspired by Les Misรฉrables (https://en.wikipedia.org/wiki/List_of_longest_novels#Comparison_of_methods) and https://nicheless.blog
@eaplmx Yeah soft limits are fine of course ๐
@eaplmx Yeah soft limits are fine of course ๐