# 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 1
# self = https://watcher.sour.is/conv/xbnx5sa
My thoughts about range requests\n\nAdditionally to pagination also range request should be used to reduce traffic.\n\nI understand that there are corner cases making this a complicated matter.\n\nI would like to see a meta header saying that the given twtxt is append only with increasing timestamps so that a simple strategy can detect valid content fetched per range request.\n\n1. read meta part per range request\n2. read last fetched twt at expected range (as known from last fetch)\n3. if fetched content starts with expected twt then process rest of data\n4. if fetched content doesn't start with expected twt discard all and fall back to fetching whole twtxt\n\nPagination (e.g. archiving old content in a different file) will lead to point 4.\n\nOf course especially pods should support range requests, correct @prologic?