Thanks for that pointer. I have watched that tag. Thanks. I do update regularly and understand security fixes are always included.
I would suggest that this is still too ordinary in terms of the challenge at hand. I remember now it was was the PHP exploit news 30 days that kicked this all off, and it hasn’t stopped.
The way I see it is - you want critical alert to get to the admin before the hack does.
Maximising user base being appraised, ready and waiting status, so the update is grabbed asap.
Reducing the time vector period of attack as quickly as possible across discourse deployments.
In summary: Force Critical update watching via the dashboard more effectively
For the exceptional moments, that are becoming all too common.
I’d call these RED BOX updates.
- exceptional CVE’s
- critically urgent
The admin won’t see often but will grab attention beyond the smiley face status points or alert icon. Attention fatigue is a real thing. Novelty must remain novel to have its alert force remain potent.