bluerobotics
frontend: add a mechanism for critical user notifications
Current behaviour
We are currently poorly set up to handle sharing the discovery of critical security vulnerabilities and safety issues, and what to do in cases of broken online infrastructure and service APIs, which is a risk to our users and their trust in BlueOS as a system.
Right now our primary courses of action are around public announcements in forum posts and adding banners to documentation and READMEs, along with releasing updates and hoping people move to them (assuming the update systems actually work...). That can miss users who are actively using their vehicles, but don't regularly perform updates.
Expected or desired behaviour
We should add a mechanism for fetching and presenting critical notifications, that's reliant on our own network infrastructure (rather than our core online service APIs).
Ideally this would be integrated with information about available releases, including as part of a more general update manager, and with the homepage dashboard.
It should further be possible to push those notifications through to a connected control station software (in case the user doesn't directly access the BlueOS interface), perhaps via MAVLink STATUS_TEXT messages, or some alternative mechanism.
Additional Context
Related to bluerobotics/cockpit#1485
Prerequisites
- [x] I have checked to make sure that a similar request has not already been filed or fixed.
