Gate 0.0.28: de blokhoogte was niet van deze app

Op verzoek van de gebruiker. Dit is een TLS-voordeur op een Electrum-server;
wat de keten doet staat in elke wallet die hij al heeft. Vier widgets over,
alle vier over deze gateway.

De leeftijd van de meting stond onder de blokhoogte en was daarmee de laatste
plek waar de pagina zei hoe oud zijn gegevens zijn: de voetregel en de badge
die hetzelfde zeiden zijn in augustus weggehaald met precies dat argument. Die
regel staat nu onder de reactietijd, na de sparkline zodat de vier onderregels
op een lijn blijven.

De rij is een raster van vier met breekpunten op 1100 en 560 pixels; vier
deelt door twee, dus de stap die bepaalde welke widget alleen kwam te staan is
vervallen. In de agent is de hoogte uit het antwoord gehaald maar het verzoek
niet: daar wordt de reactietijd uit gemeten.

Alle tests groen: 22 + 43 + 39 + 54 + 28 + 115 + 65 goed, 0 fout.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Harmen
2026-09-04 09:43:11 +02:00
co-authored by Claude Opus 5
parent 5ee21b10e7
commit dbec428e62
7 changed files with 134 additions and 80 deletions
+20 -15
View File
@@ -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.