# 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 15
# self = https://watcher.sour.is/conv/qnwhoyq
@quark I run the cron job every 15 minutes. Running it every minute imposes quite a bit of load on the feeds of other people. While jenny requests everything with the if-modified-since header set, not all servers honor that header. Most of all, yarn does not: https://git.mills.io/yarnsocial/yarn/issues/430
@quark I run the cron job every 15 minutes. Running it every minute imposes quite a bit of load on the feeds of other people. While jenny requests everything with the if-modified-since header set, not all servers honor that header. Most of all, yarn does not: https://git.mills.io/yarnsocial/yarn/issues/430
@quark I run the cron job every 15 minutes. Running it every minute imposes quite a bit of load on the feeds of other people. While jenny requests everything with the if-modified-since header set, not all servers honor that header. Most of all, yarn does not: https://git.mills.io/yarnsocial/yarn/issues/430
@movq What I would really like to see if jenny could use HTTP range requests to fetch only new content.\n\nE.g. it could refetch only last twtext line of last request to make sure it starts off at correct position.\n\nI guess there are twtxt files that only grow, then this will save a lot bandwidth over time.\n\nFor twtxt files that "forget" older content this situation would be detected and as a fallback the whole twtxt file could then be fetched.
@movq What I would really like to see if jenny could use HTTP range requests to fetch only new content.
E.g. it could refetch only last twtext line of last request to make sure it starts off at correct position.
I guess there are twtxt files that only grow, then this will save a lot bandwidth over time.
For twtxt files that "forget" older content this situation would be detected and as a fallback the whole twtxt file could then be fetched.
@movq If you implement this first I want to borrow your algorithm 🤣
@movq If you implement this first I want to borrow your algorithm 🤣