# 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 6
# self = https://watcher.sour.is/conv/3a5pggq
@lyse what is the advantage for keeping it small? Will tt/tt2 bog down if your feed isn't rotated?
@bender basically because we don't readily use or support range hunters when requesting feeds it's ideal to keep feed small for the time being at least until we think about writing up a formal specification for this, but it's also only for Http hosted feeds
@prologic I am not convinced. LOL. Can you ELI5 the problem, and what breaking the feed in smaller chunks solves?
@bender Just to save some unnecessary und useless network traffic. :-) So that I can download more 1080p videos!@1
@bender Just to save some unnecessary und useless network traffic. :-) So that I can download more 1080p videos!@1
@lyse now, that's as clear as water! See? How come @prologic wasn't able to put it that way? LOL.