# 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 19
# self = https://watcher.sour.is/conv/bk3qohq
@movq Today I had unexpected old twts after jenny -f. Have now jennys cache under revision control, automatically commiting changes after each fetch. Let's see if this helps finding a (possible) bug.
@stackeffect These didn’t happen to be the twts by jlj? His pod was unavailable or something. 🤔
@stackeffect These didn’t happen to be the twts by jlj? His pod was unavailable or something. 🤔
@stackeffect These didn’t happen to be the twts by jlj? His pod was unavailable or something. 🤔
@stackeffect One of the biiiig problems with this feature is that I don’t use it myself. I just let my mailbox grow and I honestly don’t see the need (yet) to archive or delete twts. So I don’t observe those bugs myself. 🙁 (Actually, implementing features that I don’t use myself is against one of my ground rules. If I don’t use it myself, it’s not “battle tested”. Bugs may lurk and I never find them. Hmm. I was arrogant enough this time to think: “Oh it’s such a simple feature, I can implement that, even though I don’t use it.” Maybe that was wrong.)
@stackeffect One of the biiiig problems with this feature is that I don’t use it myself. I just let my mailbox grow and I honestly don’t see the need (yet) to archive or delete twts. So I don’t observe those bugs myself. 🙁 (Actually, implementing features that I don’t use myself is against one of my ground rules. If I don’t use it myself, it’s not “battle tested”. Bugs may lurk and I never find them. Hmm. I was arrogant enough this time to think: “Oh it’s such a simple feature, I can implement that, even though I don’t use it.” Maybe that was wrong.)
@stackeffect One of the biiiig problems with this feature is that I don’t use it myself. I just let my mailbox grow and I honestly don’t see the need (yet) to archive or delete twts. So I don’t observe those bugs myself. 🙁 (Actually, implementing features that I don’t use myself is against one of my ground rules. If I don’t use it myself, it’s not “battle tested”. Bugs may lurk and I never find them. Hmm. I was arrogant enough this time to think: “Oh it’s such a simple feature, I can implement that, even though I don’t use it.” Maybe that was wrong.)
@movq Yes, it was exactly those twts. I don't think I've managed to "match" the downtime while fetching twts. But even if I had, how can this lead to inserting old twts?
Alright, for testing purposes, I deleted all twts in my box up until 2021-10-18. Let’s see how it goes.
Alright, for testing purposes, I deleted all twts in my box up until 2021-10-18. Let’s see how it goes.
Alright, for testing purposes, I deleted all twts in my box up until 2021-10-18. Let’s see how it goes.
@stackeffect Hmm, not sure. Here’s one scenario:
- You fetched jlj’s feed before you started using jenny’s new lasttwt feature.
- jlj’s pod went offline.
- You experimented a bit, archived more twts.
- jlj’s pod came back. You fetch the feed, but lasttwt is now unset, so you get all of its twts, including those that you already archived.
Dunno. It’s not *that* unlikely that it happened like this. But then of course, I have absolutely no idea what you did on your computer, so it’s just a *very* wild guess. 😅
@stackeffect Hmm, not sure. Here’s one scenario:
- You fetched jlj’s feed before you started using jenny’s new lasttwt feature.
- jlj’s pod went offline.
- You experimented a bit, archived more twts.
- jlj’s pod came back. You fetch the feed, but lasttwt is now unset, so you get all of its twts, including those that you already archived.
Dunno. It’s not *that* unlikely that it happened like this. But then of course, I have absolutely no idea what you did on your computer, so it’s just a *very* wild guess. 😅
@stackeffect Hmm, not sure. Here’s one scenario:\n\n- You fetched jlj’s feed before you started using jenny’s new lasttwt feature.\n- jlj’s pod went offline.\n- You experimented a bit, archived more twts.\n- jlj’s pod came back. You fetch the feed, but lasttwt is now unset, so you get all of its twts, including those that you already archived.\n\nDunno. It’s not *that* unlikely that it happened like this. But then of course, I have absolutely no idea what you did on your computer, so it’s just a *very* wild guess. 😅
@stackeffect Hmm, not sure. Here’s one scenario:
- You fetched jlj’s feed before you started using jenny’s new lasttwt feature.
- jlj’s pod went offline.
- You experimented a bit, archived more twts.
- jlj’s pod came back. You fetch the feed, but lasttwt is now unset, so you get all of its twts, including those that you already archived.
Dunno. It’s not *that* unlikely that it happened like this. But then of course, I have absolutely no idea what you did on your computer, so it’s just a *very* wild guess. 😅
@movq Your scenario would produce observed behaviour, agreed. On the other side I'm sure I've set very URL in lasttwt > 1630000000.0 (manually, in my editor).
But I can't reproduce any weird behaviour right now. I've tried to "blackhole" twt.nfld.uk temporarily. That does not have any effect.
I've also tried to force twt.nfld.uk to deliver an empty twtxt. That does not have any effect either.
So I guess everything is fine with jenny.
I have wrapped jenny into some shell script to versionize ~/.cache/jenney. This way I have better data if anything unexprected is showing again.
@stackeffect Strange. Well, I’ll commit that stuff to a repo now, too, it’s a good idea. 👌
@stackeffect Strange. Well, I’ll commit that stuff to a repo now, too, it’s a good idea. 👌
@stackeffect Strange. Well, I’ll commit that stuff to a repo now, too, it’s a good idea. 👌