Hello,

I’m not sure whether this is a bug, an intended feature, or in which exact release it happened, but up until my last update, all watches used to work like this:

For explanation and simplicity’s sake, let's say I mostly watch websites that change every ~2 hours, and after 24 hours since I last checked and marked all the changes I saw as viewed, I now open my self-hosted Changedetection homepage:

• I see a few pages have changed (because they are in bold) since I last opened and checked my Changedetection homepage (and since I marked all the changes I saw as viewed).
• (I always sort by “last changed” so I see all the changed pages in bold on top.)
• When I open the History of any of those changed pages and look at the “Compare from–to,” I can see that—even though the last change happened, say, 2 hours ago (before that 4 hours ago, before that 6 hours ago, and so on)—the “Compare from” part used to default to the last change I had already seen and marked as viewed when I last checked my self-hosted Changedetection homepage 24 hours ago. This made it easy to catch up from exactly where I left off, which was perfect.

NOW, it works very similarly, except the “Compare from” part defaults to the last change 2 hours ago and it “skips” all the changes I didn’t check since I last visited the homepage 24 hours ago. I then have to manually change the “Compare from” time to the last time I opened and checked my Changedetection homepage.

The problem is: if I don’t remember when I last checked, I don’t know which “Compare from” time to select to properly catch up with all the changes.

This is very similar (at least in behaviour) to #2744 —except now it seems even worse.

Thank you very much in advance! I hope my explanation comes across clearly, but if I need to clarify anything, please let me know.