# 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/f23qeya
Tried migrating to jenny... So seems it not suitable for my phone. Fetch command fetched archived feeds so i have 37k+ entries and mutt hangs for several seconds for loading this. Also i don't like hardcoded paths for config and follow file
@doesnm right, jenny isn't the problem, it's your platform of choice. The fetching of archives doesn't happen all time (once only, right @movq?), but yes, depending on the amount of feeds you follow that first time might take a while.
@bender Right, it fetches archived feeds on the first run (because it wants to grab all twts from that feed). Later on, it keeps track of the last seen twt hash per feed – if it cannot find that hash anymore, then it concludes that the feed must have been rotated/archived, so it fetches some/all archived feeds again until it finds that twt hash. Easy, right? 😅
@bender Right, it fetches archived feeds on the first run (because it wants to grab all twts from that feed). Later on, it keeps track of the last seen twt hash per feed – if it cannot find that hash anymore, then it concludes that the feed must have been rotated/archived, so it fetches some/all archived feeds again until it finds that twt hash. Easy, right? 😅
@bender Right, it fetches archived feeds on the first run (because it wants to grab all twts from that feed). Later on, it keeps track of the last seen twt hash per feed – if it cannot find that hash anymore, then it concludes that the feed must have been rotated/archived, so it fetches some/all archived feeds again until it finds that twt hash. Easy, right? 😅
@bender Right, it fetches archived feeds on the first run (because it wants to grab all twts from that feed). Later on, it keeps track of the last seen twt hash per feed – if it cannot find that hash anymore, then it concludes that the feed must have been rotated/archived, so it fetches some/all archived feeds again until it finds that twt hash. Easy, right? 😅