# 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 16
# self = https://watcher.sour.is/conv/gtumowq
@movq I don't know, but some days ago we got this as the best clue. Not sure why this twt doesn't show up in the yarn for that topic, maybe some limit evicted it from the cachee in the meantime.
@lyse you are right, thatβs weird. As I understand it, the cache is supposed to populate if older twts and brought up.
Is there a way to control how big of a cache to keep, @prologic? Because I would like to extend mine two, or three times more. That is, to cache more things, for longer.
@movq back to the question. He got upset because he was told to get a job when he was begging for a donation, and simply left.
@fastidious Yes. there is a --flag for it. i have mine set for some crazy long time.
@fastidious Yes. there is a --flag for it. i have mine set for some crazy long time.
@xuu tell me flag, for Pete sake! Help me out! π
@lyse bingo! That exact one. We joked around, and @prologic actually recommended something useful, as you can see. Sadly not well taken. π
@fastidious That yarn was indeed *VERY* funny to read. :'-D @thecanine started it off brilliantly! Yes, unfortunately, the only useful comment hit him somehow hard.
@fastidious @lyse Uhh, I see. π€ π Well, jobs and finances are a delicate subject β¦
@fastidious @lyse Uhh, I see. π€ π Well, jobs and finances are a delicate subject β¦
@fastidious @lyse Uhh, I see. π€ π Well, jobs and finances are a delicate subject β¦
@movq No doubt, they are. On the other hand he was always the one who said, that people shouldn't interpret things into messages that aren't there. So to me it appears that @adi didn't live by his own "rule" that time. I truely cannot imagine that @prologic wanted to be rude and scare him off. In any case, it's a pity how it went.