Jared: only for users of matrix.lotusguild.org; tie into Uptime Kuma at https://isitup.lotusguild.org/status/public tracking the homeserver and its sub-services. "Entire sprint, lots of planning, cannot get it wrong."
Facts to design around
Matrix has no scheduled-maintenance signal. Two standard-ish carriers exist: Server Notices (m.server_notice rooms, Synapse admin API — already rendered by Lotus) for the human-readable message, and nothing at all for a machine-readable countdown.
Uptime Kuma exposes a public JSON for a status page: GET /api/status-page/<slug> (monitor groups + maintenance windows with start/end/title/description) and GET /api/status-page/heartbeat/<slug> (current up/down per monitor). Scheduled maintenance is a first-class Kuma feature (Maintenance → schedule → attach to the status page). That gives us the countdown without inventing a Matrix event.
Proposed shape (to be planned, not built yet)
config.json: statusPages: { "matrix.lotusguild.org": "https://isitup.lotusguild.org/api/status-page/public" } — keyed by homeserver, so nothing is hardcoded and other homeservers simply have no banner.
Client polls the JSON (every 5 min, backoff on error, only when the tab is visible). Active/upcoming maintenance → a slim top strip: "Scheduled maintenance: Matrix restarts in 42 min (22:00–22:15)". Any core monitor down (Synapse / LiveKit / lk-jwt / media) → "Voice calls are currently down — we know" strip, so people stop DMing you.
Dismiss per maintenance id; never blocks the UI; degrades to nothing if Kuma is unreachable (Kuma being down must not look like Matrix being down).
Security/privacy: read-only public JSON, no auth, no cookies; CSP connect-src needs the isitup origin added (docker-nginx.conf + prod nginx). The client sends nothing.
Which monitors count as "core" is a Kuma group name (e.g. group "Matrix core") so you control it from Kuma, not from code.
Open questions for Jared (before any code)
Which Kuma monitors/groups map to "Matrix is down" vs "just degraded"?
Banner for upcoming maintenance: how far ahead (24 h? 1 h?)
Should the desktop app also fire an OS notification 10 min before a window?
Do you also want to keep sending a Server Notice for the message body, or let the Kuna description be the message?
Jared: only for users of `matrix.lotusguild.org`; tie into Uptime Kuma at https://isitup.lotusguild.org/status/public tracking the homeserver and its sub-services. "Entire sprint, lots of planning, cannot get it wrong."
### Facts to design around
- Matrix has no scheduled-maintenance signal. Two standard-ish carriers exist: **Server Notices** (`m.server_notice` rooms, Synapse admin API — already rendered by Lotus) for the human-readable message, and nothing at all for a machine-readable countdown.
- Uptime Kuma exposes a **public JSON** for a status page: `GET /api/status-page/<slug>` (monitor groups + *maintenance* windows with `start`/`end`/`title`/`description`) and `GET /api/status-page/heartbeat/<slug>` (current up/down per monitor). Scheduled maintenance is a first-class Kuma feature (Maintenance → schedule → attach to the status page). That gives us the countdown **without inventing a Matrix event**.
### Proposed shape (to be planned, not built yet)
- `config.json`: `statusPages: { "matrix.lotusguild.org": "https://isitup.lotusguild.org/api/status-page/public" }` — keyed by homeserver, so nothing is hardcoded and other homeservers simply have no banner.
- Client polls the JSON (every 5 min, backoff on error, only when the tab is visible). Active/upcoming **maintenance** → a slim top strip: "Scheduled maintenance: Matrix restarts in 42 min (22:00–22:15)". Any core monitor **down** (Synapse / LiveKit / lk-jwt / media) → "Voice calls are currently down — we know" strip, so people stop DMing you.
- Dismiss per maintenance id; never blocks the UI; degrades to nothing if Kuma is unreachable (Kuma being down must not look like Matrix being down).
- Security/privacy: read-only public JSON, no auth, no cookies; CSP `connect-src` needs the isitup origin added (docker-nginx.conf + prod nginx). The client sends nothing.
- Which monitors count as "core" is a Kuma **group** name (e.g. group "Matrix core") so you control it from Kuma, not from code.
### Open questions for Jared (before any code)
1. Which Kuma monitors/groups map to "Matrix is down" vs "just degraded"?
2. Banner for *upcoming* maintenance: how far ahead (24 h? 1 h?)
3. Should the desktop app also fire an OS notification 10 min before a window?
4. Do you also want to keep sending a Server Notice for the message body, or let the Kuna description be the message?
These are screenshots of the actual Lotus Chat client: the current lotus code plus a prototype of the banner, on a local branch (server-status-banner) that isn't pushed or deployed. The app ran logged in to a local test homeserver.
Kuma was simulated: its two status-page URLs were answered with fake data for each state.
Server down: this client's sync connection was also cut.
Leaves: the falling leaves are the app's live autumn theme.
Only one strip shows at a time, in the same slot as the existing "Connecting…" and clock banners. When several apply, the one listed first here wins.
1 · Server down
The connection is lost and Kuma says the Homeserver group is down. Red, can't be dismissed. It replaces today's "Connection Lost!".
2 · Server having problems
Kuma says the Homeserver group is down, but this client is still connected. Amber, can't be dismissed.
3 · Maintenance in progress
The title and end time come from the Kuma maintenance window, shown in the viewer's timezone. Details shows the Kuma description.
4 · Voice calls down
Kuma's Voice calls group is down. Dismissable until it recovers. There's also a note above Join.
5 · Announcement
An incident posted on the Kuma status page. The colour follows the incident style (info, warning or danger). Dismissable; it comes back if you edit it.
6 · Sign-in problems (login screen only)
Dark theme and phone
Behaviour
Scope: only for matrix.lotusguild.org. The config is keyed by homeserver, so users of other servers never contact Kuma.
What counts as down: a group is down when any of its monitors fails 2 checks in a row. For example, if the call token service is down, calls are down even while LiveKit is up.
Polling: every 5 min while the app is visible; every 60 s while a problem strip is showing; and at once when the connection drops.
Kuma unreachable: if Kuma can't be reached or returns something unexpected, no strip.
Your call
Wording of each strip.
Should 2 (server having problems) show at all?
Do you want a short green "Back to normal" strip after an outage ends? (Not built yet.)
Kuma setup: a status page with slug matrix and groups Homeserver, Voice calls and Login. Kuma is LXC 101 on monitor-02. Either you create them in the Kuma UI, or you give me a temporary admin login and I do it through Kuma's API.
## Design review: screenshots of the real client
These are **screenshots of the actual Lotus Chat client**: the current `lotus` code plus a prototype of the banner, on a local branch (`server-status-banner`) that isn't pushed or deployed. The app ran logged in to a local test homeserver.
- **Kuma was simulated:** its two status-page URLs were answered with fake data for each state.
- **Server down:** this client's sync connection was also cut.
- **Leaves:** the falling leaves are the app's live autumn theme.
Only **one strip shows at a time**, in the same slot as the existing "Connecting…" and clock banners. When several apply, the one listed first here wins.
### 1 · Server down
The connection is lost **and** Kuma says the Homeserver group is down. Red, can't be dismissed. It replaces today's "Connection Lost!".
### 2 · Server having problems
Kuma says the Homeserver group is down, but this client is still connected. Amber, can't be dismissed.
### 3 · Maintenance in progress
The title and end time come from the Kuma maintenance window, shown in the viewer's timezone. **Details** shows the Kuma description.
### 4 · Voice calls down
Kuma's Voice calls group is down. Dismissable until it recovers. There's also a note above **Join**.
### 5 · Announcement
An incident posted on the Kuma status page. The colour follows the incident style (info, warning or danger). Dismissable; it comes back if you edit it.
### 6 · Sign-in problems (login screen only)
### Dark theme and phone
### Behaviour
- **Scope:** only for `matrix.lotusguild.org`. The config is keyed by homeserver, so users of other servers never contact Kuma.
- **What counts as down:** a group is down when **any** of its monitors fails **2 checks in a row**. For example, if the call token service is down, calls are down even while LiveKit is up.
- **Polling:** every 5 min while the app is visible; every 60 s while a problem strip is showing; and at once when the connection drops.
- **Kuma unreachable:** if Kuma can't be reached or returns something unexpected, **no strip**.
### Your call
1. Wording of each strip.
2. Should **2** (server having problems) show at all?
3. Do you want a short green "Back to normal" strip after an outage ends? (Not built yet.)
4. Kuma setup: a status page with slug `matrix` and groups **Homeserver**, **Voice calls** and **Login**. Kuma is LXC 101 on monitor-02. Either you create them in the Kuma UI, or you give me a temporary admin login and I do it through Kuma's API.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Jared: only for users of
matrix.lotusguild.org; tie into Uptime Kuma at https://isitup.lotusguild.org/status/public tracking the homeserver and its sub-services. "Entire sprint, lots of planning, cannot get it wrong."Facts to design around
m.server_noticerooms, Synapse admin API — already rendered by Lotus) for the human-readable message, and nothing at all for a machine-readable countdown.GET /api/status-page/<slug>(monitor groups + maintenance windows withstart/end/title/description) andGET /api/status-page/heartbeat/<slug>(current up/down per monitor). Scheduled maintenance is a first-class Kuma feature (Maintenance → schedule → attach to the status page). That gives us the countdown without inventing a Matrix event.Proposed shape (to be planned, not built yet)
config.json:statusPages: { "matrix.lotusguild.org": "https://isitup.lotusguild.org/api/status-page/public" }— keyed by homeserver, so nothing is hardcoded and other homeservers simply have no banner.connect-srcneeds the isitup origin added (docker-nginx.conf + prod nginx). The client sends nothing.Open questions for Jared (before any code)
Design review: screenshots of the real client
These are screenshots of the actual Lotus Chat client: the current
lotuscode plus a prototype of the banner, on a local branch (server-status-banner) that isn't pushed or deployed. The app ran logged in to a local test homeserver.Only one strip shows at a time, in the same slot as the existing "Connecting…" and clock banners. When several apply, the one listed first here wins.
1 · Server down
The connection is lost and Kuma says the Homeserver group is down. Red, can't be dismissed. It replaces today's "Connection Lost!".
2 · Server having problems
Kuma says the Homeserver group is down, but this client is still connected. Amber, can't be dismissed.
3 · Maintenance in progress
The title and end time come from the Kuma maintenance window, shown in the viewer's timezone. Details shows the Kuma description.
4 · Voice calls down
Kuma's Voice calls group is down. Dismissable until it recovers. There's also a note above Join.
5 · Announcement
An incident posted on the Kuma status page. The colour follows the incident style (info, warning or danger). Dismissable; it comes back if you edit it.
6 · Sign-in problems (login screen only)
Dark theme and phone
Behaviour
matrix.lotusguild.org. The config is keyed by homeserver, so users of other servers never contact Kuma.Your call
matrixand groups Homeserver, Voice calls and Login. Kuma is LXC 101 on monitor-02. Either you create them in the Kuma UI, or you give me a temporary admin login and I do it through Kuma's API.