# 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 10
# self = https://watcher.sour.is/conv/36xvvca
Found and fixed yet another bug in my twtxt feed archive rotater.
@lyse Quite a lot of bugs in that area. 🤔 I mean in general, not just in your client. What was it? Sometimes it almost feels like we went too far with that spec and made it too complicated / too many corner cases.
@lyse Quite a lot of bugs in that area. 🤔 I mean in general, not just in your client. What was it? Sometimes it almost feels like we went too far with that spec and made it too complicated / too many corner cases.
@lyse Quite a lot of bugs in that area. 🤔 I mean in general, not just in your client. What was it? Sometimes it almost feels like we went too far with that spec and made it too complicated / too many corner cases.
@movq Generating the September 2022 archive feed somehow referenced itself as previous feed (including its last twt hash) rather than the one from August. Don't really understand how that could happen, but I now explicitly ignore the about to be newly rotated archive feed when looking for the most recent already present archive feed.
I also have to look into something related tomorrow. The script will always generate a new archive feed with each run, even though the minimum number of months to keep in the main feed was not reached. Example: Main feed contains everthing from 1st October 2022, executing "archive main feed and keep at least last five months in main feed" will still generate an archive feed for October 2022. Obviously, nothing should have happened at all.
With the last rotation I started version controlling my feed files in git. My archiver script also still doesn't touch the main feed. Currently, it only writes the archive feed files and I have to remove the rotated twts from the main feed and copy the printed prev = filename hash line by hand. Without that manual step I would not have caught the reference error.
@lyse I think the spec is okay 👌
@lyse I think the spec is okay 👌
@lyse I think the spec is okay 👌
@lyse I think the spec is okay 👌
@prologic Yeah, the spec isn't too bad. What's really nice actually, that you do not have to touch already written archive feeds when rotating again. With a doubly linked feed list to jump forward (# next = hash filename) that would be a wee bit more complex. The only thing to simplify with the current approach would be to strip away the hash and only use the filename (but that's really not an issue). The bugs definitely have to do with my great programming skills. ;-)