On Monday, 4 May 2026 at 13:29:22 UTC, libxmoc wrote:
I prefer the old version, it's easier to read vertically and
had more details.
Thanks for honest the feedback!
Much appreciated :)
Old status page
---------------
First and foremost, the old status page isn’t going anywhere.
It’s set up using a feature provided by updown.io as part of
their SaaS offering for free of (additional) charge complementary
to their monitoring service.
Regarding the visible details
-----------------------------
• There is a table view showing all monitored endpoints with a
few details: <https://status.dlang.rocks/checks>
• I’m limited to what data I can gather using their API.
Unfortunately, that outright lacks certain details (i.a. HTTP/2
availability, IPv4/IPv6 availability). Others are only readable
using a write-enabled API key. (I’ve opened a feature request
regarding this, but they are wary adding another API key type;
while I’m wary adding full access API key to an app that is only
supposed to have read-only access.)
• From my perspective, a status page is primarily supposed to
provide a quick overview about which services are down (and which
are up). That’s why the dashboard (which serves as a front page)
is designed the way it is.
• The “grid” view of the dashboard actually consists of two
grids: One for services that are down, one for services that are
up. (Thought I’d add this fact, as it’s only observable in
situations where something is down.)
• I will experiment with a “list” view for the dashboard. Thank
you for this idea.
