Closed mrose17 closed 2 years ago
Option 1. If we updated status.brave.com with the notice, there's an API to obtain the current status values - https://status.brave.com/api/v2/summary.json. Of course, we'd have to weigh up whether introducing a call to that url from talk.brave.com justifies providing the feedback.
Option 2. There are also more managed options from statuspage for providing that feedback - https://support.atlassian.com/statuspage/docs/embed-status-updates-to-other-pages/, though I suspect that the extra third party dep this would introduce makes this an unattractive approach.
Option 3. Alternatively, for big emergencies only, we could just embed an urgent message in the code and re-release, since the release of talk.brave.com takes less than 1 minute. If we wanted to take that approach we should prepare the logic so that setting the setting the message is just a matter of updating a constant string and we're not trying to prepare UI logic etc during an emergency.
Option 1 (summary.json) doesn't seem so bad if we can load/parse asynchronously and then call notice
Option 3 (edit-deploy) seems duplicative given that we probably want to change the status site as well.
Option 1 seems sensible to me. To implement, we'll need to:
https://status.brave.com
as a connect-src
- this appears to have already been done@tackley - i confirm option 1.
Verified PASSED
on dev (and staging).
Confirmed link to (Brave's) Service Status
(https://status.brave.com/
) appears at the bottom right of the footer, on https://talk.brave.software/
and https://talk.bravesoftware.com
:
The question is where to get the data from...