Total recoding of the notification system! Notifications only available from the steemnotify.me website for the next day. The browser extensions and Android app will be offline in that time.
It's getting crowded in here
I've remodelled the whole notification system to ease pressure on the back end database that was hanging at points when there were too many corresponding read, write and delete operations going on. This has involved moving most of the processing - to determine what is and isn't a notification - from the client end (i.e you) to the server end (i.e. me). This is great for you for two reasons - less bandwidth and less power consumption. And importantly for the database it allows me to better control when read and write operations are going on.
Given there are three iterations of this app (website, browser extensions, and Android app), it requires me to essentially recode all three apps separately (as they all use a different model to interact with the server due to their inherent differences). The website is done, and I want to test it in a production environment to make sure it is stable and performant. While it is testing for the next 12-24 hours or so, I'll recode the browser extensions and android app. Assuming the test works ok, I'll update the extensions and android app in short order.
I'll update again when that is done. But for now, if you want to continue getting notifications, get them from the steemnotify.me website. Cheers!