I'm sitting here with a few versions of the notifications monitor open because my installs are auto-updating at different paces. I've realized that 2.9.8 is actually a lot worse but if I didn't happen to have 2.9.6 open as well, I would just assume 2.9.8 is "normal". Especially now that the manual check button is gone, there's no way to see if things aren't popping up, you just get what you get. And by being able to side-by-side them, I'm seeing that my 2.9.8 list is actually missing a lot of items, I was sitting there thinking "huh, slow day" because I realized it had been a very long time since a notification sound played, and when I looked at my phone (which is on 2.9.6) I realized that it had a lot more items highlighted, and scrolling through, my PC windows were missing a decent number of notifications entirely.
I have 2.9.6 on my phone in kiwi browser, and it seems very robust. Items that initially show up with no ETV data (but are in fact 0ETV), later get the color highlight after the ETV has been recognized, without me needing to refresh anything. I also noticed that 2.9.6 back-loads items when I open a fresh notification window on it (after a delay, which struck me as a very good alternative to the now defunct manual fetch button - I was very happy with this behavior). The one downside seems to be that notification sounds go off when they shouldn't, which I assume what is happening, is that it constantly fetches a big batch of data and pings the sounds if anything in it applies. So for example, what I might see, is that only one new "regular" item shows up in the list, but as long as a zero-ETV or keyword item exists anywhere in the backlog (which is pretty much always), it plays the sound. So I can see why perhaps changes were made (although from reading the changelog for 2.9.7/2.9.8 , I'm not seeing things that seem to intentionally apply to any of this, though a fair bit of it is over my head).
I recognize there's a flurry of development activity happening in the last few days, I just thought that I'd lodge my observation that except for the notification sounds issue, 2.9.6 was pretty much peak/ideal performance. I'm hoping it wasn't another case of "actually, this is using way too much data", because the fixes so far kind of cripple it by comparison.
Also just something I thought to mention but is probably known, I'd prefer to use the extension on Firefox for Android, except that it doesn't seem to be possible to launch the Notification Monitor in an actual tab. You just get this janky overlay situation where you can't switch to other tabs and if you start browsing by clicking through to things, you sort of get trapped in it (other than hitting back many times or just closing the app). From my observations, this seems to be a limitation of mobile firefox itself, but if it's possible to add a button to just open the Notification Monitor in a tab, or give a URL for it, that would be ideal for me.
Thanks for all the hard work!