-
+ checked" staat als "as of ... ago" onder de reactietijd. -->
${APP_ELECTRS_NODE_IP}:${APP_ELECTRS_NODE_PORT}
Backend response
@@ -973,16 +984,7 @@ body {
-
-
-
@@ -1275,8 +1277,8 @@ body {
+ gegevens staat al onder de reactietijd, en het versienummer is ook in
+ umbrelOS zelf te zien. -->
@@ -1403,9 +1405,9 @@ body {
function show(id, on) { el(id).classList.toggle('hidden', !on); }
- function num(n) {
- return String(n).replace(/\B(?=(\d{3})+(?!\d))/g, ' ');
- }
+ // Hier stond num(), dat een getal met spaties per duizend afbrak. De
+ // blokhoogte was de enige waarde die groot genoeg was om dat te vragen, en die
+ // widget is er sinds 0.0.28 uit.
function whenLocal(unix) {
if (!unix) { return null; }
@@ -1427,7 +1429,7 @@ body {
// Hoe oud de gegevens zijn, hangt niet meer aan een melding of een badge. Dat
// is twee keer op verzoek van de gebruiker weggehaald: de melding bovenaan op
// 19-08-2026, de badge bij de Electrum-server op 20-08-2026. Wat het zegt staat
- // nog op de plek waar het thuishoort, namelijk onder de blokhoogte als
+ // nog op de plek waar het thuishoort, namelijk onder de reactietijd als
// "as of ... ago" en in de rij "Last checked".
//
// De leeftijd zelf blijft dus in gebruik, alleen niet meer als aparte
@@ -1440,15 +1442,11 @@ body {
drawSetup(tls.domain, tls.port);
- // Blokhoogte
- if (typeof backend.height === 'number') {
- put('stat-height', num(backend.height));
- el('stat-height-sub').textContent = age !== null ? 'as of ' + agoText(age) : '';
- }
-
- // Reactietijd
+ // Reactietijd. De onderregel met de leeftijd van de meting stond tot 0.0.28
+ // onder de blokhoogte; die widget is eruit en de regel staat nu hier.
if (typeof backend.response_ms === 'number') {
put('stat-latency', backend.response_ms, ' ms');
+ el('stat-latency-sub').textContent = age !== null ? 'as of ' + agoText(age) : '';
}
drawSpark(s.history || []);
@@ -1499,7 +1497,7 @@ body {
drawCertChoices(s.certificates, cert.selected, nowSec);
// Backend. "Last checked" stond hier als derde lijstregel en is er op
- // 27-08-2026 uit: hetzelfde staat onder de blokhoogte als "as of ... ago",
+ // 27-08-2026 uit: hetzelfde staat onder de reactietijd als "as of ... ago",
// en een widget met drie onderteksten is geen widget meer.
put('backend-name', backend.name);
if (backend.address) { put('backend-address', backend.address); }
diff --git a/whatsnext-electrum-gate/umbrel-app.yml b/whatsnext-electrum-gate/umbrel-app.yml
index 7eaf517..2fb77e0 100644
--- a/whatsnext-electrum-gate/umbrel-app.yml
+++ b/whatsnext-electrum-gate/umbrel-app.yml
@@ -9,7 +9,7 @@ manifestVersion: 1
id: whatsnext-electrum-gate
category: bitcoin
name: Electrum Gate
-version: "0.0.27"
+version: "0.0.28"
tagline: Your own node from anywhere, without waiting for Tor
description: >-
The privacy win is already yours: you run the Electrum server. A public one gets asked for
@@ -42,9 +42,9 @@ description: >-
it, they already reach the Electrum server directly.
- The dashboard hands you the exact line each of those wallets asks for, and shows block
- height, certificate expiry and whether your Electrum server is answering. Electrs, Fulcrum
- and ElectrumX all work, switchable in the umbrelOS settings.
+ The dashboard hands you the exact line each of those wallets asks for, and shows how long
+ your certificate is still good for and whether your Electrum server is answering. Electrs,
+ Fulcrum and ElectrumX all work, switchable in the umbrelOS settings.
What it does not do: hide that the traffic exists. Your domain is public in the certificate
@@ -56,6 +56,16 @@ description: >-
# staan. In 0.0.9 stond er daardoor drie keer "Earlier releases" en twee keer
# dezelfde 0.0.4-regel. De toets let er nu op.
releaseNotes: >-
+ The block height tile is gone. This app is a front door for your Electrum server; what the chain is
+ doing is not its news to report, and every wallet and block explorer you own already tells you. Four
+ tiles are left, all of them about this gateway: which server your traffic goes to, whether it answers
+ and how fast, how long your certificate is still good for, and whether the front door itself is up.
+ How old the readings are now sits under the response time, where it used to sit under the height.
+
+
+ Everything in 0.0.27:
+
+
Fixes the Status card reading "Not answering" for five minutes after every restart or update, with
a connection error underneath, while the gateway itself was working fine the whole time. The check
runs from inside the app and it ran before the part it checks had started, so the very first
@@ -82,20 +92,15 @@ releaseNotes: >-
changed.
- Everything in 0.0.24, released the day before:
-
-
- The menu has a new "About this app" item: what the app is for, what it asks of you, and what the
- Status card does and does not prove. That last one was the reason for this release. The card used to
- read "Answering" with "answered in 7 ms, from inside the app" underneath, which was unclear in both
- halves. It now says "Running", with the measurement below it, and the caveat has moved to where there
- is room to state it properly: the check runs inside the app, so a router that no longer forwards the
- port still reads as Running here.
-
-
Earlier releases:
+ 0.0.24 added an "About this app" item to the menu, and changed the Status card from "Answering" with
+ "answered in 7 ms, from inside the app" underneath to "Running" with the measurement below it. The
+ caveat moved into that dialog, where there is room to state it: the check runs inside the app, so a
+ router that no longer forwards the port still reads as Running here.
+
+
0.0.23 fixed a page that could go blank or show stale values once another app from the same store was
installed. The page reached its helper by a short name that a second app happened to use as well, so
roughly half of its requests ended up at the wrong one.