# 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 5
# self = https://watcher.sour.is/conv/icfdqqa
Correct, @bender. Since the very beginning, my twtxt flow is very flawed. But it turns out to be an advantage for this sort of problem. :-) I still use the official (but patched) twtxt client by buckket to actually fetch and fill the cache. I think one of of the patches played around with the error reporting. This way, any problems with fetching or parsing feeds show up immediately. Once I think, I've seen enough errors, I unsubscribe.
tt is just a viewer into the cache. The read statuses are stored in a separate database file.
It also happened a few times, that I thought some feed was permanently dead and removed it from my list. But then, others mentioned it, so I resubscribed.
Let me take this opportunity to recommend something to @bmallred: https://staystrong.run/user/bmallred/twtxt.txt returned 200 but no Last-Modified header - can’t cache content :-)
Another modification I made is to actually cache it anyways. Otherwise, tt wouldn't show anything. I implemented that for some other feed that doesn't exist anymore.
@lyse ah, if only you were to finally clean up that code, and make that client widely available...! One can only dream, right? :-)
@lyse ah, if only you were to finally clean up that code, and make that client widely available...! One can only dream, right? :-)
@quark It's a giant mess at the moment. I started rewriting it from scratch in January last year. But that's also a big undertaking. And that's why I stopped. I should proceed, though. Let's see.