releases: sync Hermes 0.3.1 from the live manifest, regenerate pages
This commit is contained in:
Local Dev
parent
75d377e87e
commit
bcc2d8cf64
3 changed files with 87 additions and 87 deletions
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"schema": "silentmode-releases/2",
|
||||
"updated": "2026-10-24T00:26:19.725Z",
|
||||
"updated": "2026-10-24T01:05:15.609Z",
|
||||
"mirrors": [
|
||||
"https://dl.silentmode.st/"
|
||||
],
|
||||
|
|
@ -60,6 +60,21 @@
|
|||
"AriadneResolver-Setup-0.1.13.exe": "a16d10759efede4412f4fdb52d59424bf56bbb258bb002ab930f4a5a5aef8a41"
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": "ariadne-android",
|
||||
"product": "Ariadne for Android",
|
||||
"version": "0.53",
|
||||
"date": "2026-10-24",
|
||||
"platform": "android",
|
||||
"minSdk": 21,
|
||||
"signed": true,
|
||||
"signingAuthority": null,
|
||||
"signingCertSha256": "46ebbbe5dc73148d66410fd0337b1e6683472128c983e8e2578200b9e3ca548c",
|
||||
"changes": "Settings page is now a short menu of 11 labeled sections — one row-card per topic, with its icon and chevron. Tap a row to see that section on its own with a ‹ Settings back link; the URL hash remembers where you are, so toggles inside a section no longer bounce you back to the top. Same signing key; installs over 0.52.",
|
||||
"files": {
|
||||
"ariadne-v0.53.apk": "6adedfd3f0e4c5742b79ac25f4575e03d2b0f8819785667e22f3a7d8eaad1c48"
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": "ariadne-android",
|
||||
"product": "Ariadne for Android",
|
||||
|
|
@ -90,21 +105,6 @@
|
|||
"ariadne-v0.51.apk": "8e5b091bf48ffe17047f91e517e9ca66e8ff4c4cdcb1a074f7b928654eae2b45"
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": "ariadne-android",
|
||||
"product": "Ariadne for Android",
|
||||
"version": "0.50",
|
||||
"date": "2026-10-23",
|
||||
"platform": "android",
|
||||
"minSdk": 21,
|
||||
"signed": true,
|
||||
"signingAuthority": null,
|
||||
"signingCertSha256": "46ebbbe5dc73148d66410fd0337b1e6683472128c983e8e2578200b9e3ca548c",
|
||||
"changes": "New launcher icon — the laurel-crowned bust silhouette from the Ariadne.X brand kit, recoloured gold on navy. Replaces the figure-only mark; same signing key; installs over 0.49.",
|
||||
"files": {
|
||||
"ariadne-v0.50.apk": "4ca980c58a21101f2b3b54a864a49f71912d424d07870778da21690efb45e35b"
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": "pithos-desktop",
|
||||
"product": "Pithos",
|
||||
|
|
@ -193,21 +193,6 @@
|
|||
"hermes-v0.2.2.apk": "b46da998caa57a6923bb4ab305c5ab1cff88fbf38f4028eb2cecceb77140f1a6"
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": "hermes-android",
|
||||
"product": "Hermes for Android",
|
||||
"version": "0.2.1",
|
||||
"date": "2026-10-24",
|
||||
"platform": "android",
|
||||
"minSdk": 26,
|
||||
"signed": true,
|
||||
"signingAuthority": null,
|
||||
"signingCertSha256": "b1e4685a7476fcbb3b53d807e298dea2ef2c7375f240cf04847d3d712cab95b7",
|
||||
"changes": "Fix: real-time inbox delivery. 0.2.0 held a persistent inbox REQ at sign-in, but mobile WebSockets drop constantly (wifi/cellular transitions, OS backgrounding, keep-alive timeouts) and the REQ wasn't replayed on reconnect — the relay forgot our filter and inbound kind:1059 wraps stopped arriving until the next 15-min WorkManager poll or next outgoing send kicked a catch-up. RelayConnection now remembers active subscriptions and replays them on every onOpen, so a recipient sees messages the moment they land on the relay. Also pins the initial `since` to max(lastSeenAt, now - 7d), bounding the reconnect replay. Updates DeliveryPrefs.lastSeenAt on each decrypted wrap so background delivery stays in step.",
|
||||
"files": {
|
||||
"hermes-v0.2.1.apk": "014438c3c1a92dd0108d994ae411ed27bf2de58c735614498e86d11462066d61"
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": "hermes-desktop",
|
||||
"product": "Hermes for Windows",
|
||||
|
|
@ -221,6 +206,21 @@
|
|||
"Hermes-0.1.0-setup.exe": "0adc742d54daaee2b62e7fdcbff2f0203bd50f995444487ff93233ccc6328552",
|
||||
"Hermes-0.1.0.msi": "fa81948bba8c3d6e9306a5aa218424fd2a4bc692891f3d2543c2782207f86b3f"
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": "hermes-android",
|
||||
"product": "Hermes for Android",
|
||||
"version": "0.3.1",
|
||||
"date": "2026-10-24",
|
||||
"platform": "android",
|
||||
"minSdk": 26,
|
||||
"signed": true,
|
||||
"signingAuthority": null,
|
||||
"signingCertSha256": "b1e4685a7476fcbb3b53d807e298dea2ef2c7375f240cf04847d3d712cab95b7",
|
||||
"changes": "Fix: phone verify over Telegram no longer gets stuck. Two live bugs. First, Android 11+ package visibility was blocking the tg:// deep link — the OS silently fell through to a browser (or threw) even with Telegram installed, so our startActivity could never actually dispatch /start to the bot; fixed by declaring the tg:// and https://t.me intents in the manifest <queries> block. Second, the https://t.me/<bot>?start=<nonce> URL only auto-sends /start on a brand-new chat with the bot — once you had opened the bot even once (common after a first verify attempt), the chat reopened with no Share-Phone button and no retry path; Hermes now prefers tg://resolve, which fires /start regardless of chat state. Polling also starts the moment a nonce is minted (not only on return from Telegram), honours the server's 10-minute nonce TTL instead of giving up at three, and the pane now carries Check-status-now / Reopen-Telegram-chat / Cancel-and-start-over controls so a stale verify can be unstuck without leaving the screen.",
|
||||
"files": {
|
||||
"hermes-v0.3.1.apk": "f3ebaea886cc363e131027514dd038343e522d31296b8dfdd46af1889c095637"
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
|
|
|
|||
|
|
@ -111,6 +111,20 @@
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Ariadne for Android <span style="color:var(--acid)">0.53</span></h2>
|
||||
<div class="meta">Android 5.0+ (API 21) · self-signed release key · 2026-10-24 · Settings page is now a short menu of 11 labeled sections — one row-card per topic, with its icon and chevron. Tap a row to see that section on its own with a ‹ Settings back link; the URL hash remembers where you are, so toggles inside a section no longer bounce you back to the top. Same signing key; installs over 0.52.</div>
|
||||
|
||||
<div class="file">
|
||||
<div class="n"><a href="https://dl.silentmode.st/ariadne-v0.53.apk">ariadne-v0.53.apk</a> — APK</div>
|
||||
<code>6adedfd3f0e4c5742b79ac25f4575e03d2b0f8819785667e22f3a7d8eaad1c48</code>
|
||||
</div>
|
||||
<div class="file">
|
||||
<div class="n">Signing certificate — SHA-256 (the same key signs every future release)</div>
|
||||
<code>46ebbbe5dc73148d66410fd0337b1e6683472128c983e8e2578200b9e3ca548c</code>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Ariadne for Android <span style="color:var(--acid)">0.52</span></h2>
|
||||
<div class="meta">Android 5.0+ (API 21) · self-signed release key · 2026-10-24 · The updater now polls ariadne.x — manifest + APKs live in the s3://bns/ariadne/ bucket the on-chain record points to, routed through the public BNS gateway so a raw HTTPS client reaches them without the Ariadne resolver being up. Download page link also moved from silentmode.st to ariadne.x. Older clients keep polling the silentmode.st mirror; the manifest at both URLs stays in sync until the fleet has rolled over. Same signing key; installs over 0.51.</div>
|
||||
|
|
@ -139,20 +153,6 @@
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Ariadne for Android <span style="color:var(--acid)">0.50</span></h2>
|
||||
<div class="meta">Android 5.0+ (API 21) · self-signed release key · 2026-10-23 · New launcher icon — the laurel-crowned bust silhouette from the Ariadne.X brand kit, recoloured gold on navy. Replaces the figure-only mark; same signing key; installs over 0.49.</div>
|
||||
|
||||
<div class="file">
|
||||
<div class="n"><a href="https://dl.silentmode.st/ariadne-v0.50.apk">ariadne-v0.50.apk</a> — APK</div>
|
||||
<code>4ca980c58a21101f2b3b54a864a49f71912d424d07870778da21690efb45e35b</code>
|
||||
</div>
|
||||
<div class="file">
|
||||
<div class="n">Signing certificate — SHA-256 (the same key signs every future release)</div>
|
||||
<code>46ebbbe5dc73148d66410fd0337b1e6683472128c983e8e2578200b9e3ca548c</code>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Pithos <span style="color:var(--acid)">0.3.26</span></h2>
|
||||
<div class="meta">Windows 64-bit · unsigned · 2026-10-08 · In Theseus, Send on Telegram and Send on WhatsApp open Theseus's own Telegram and WhatsApp apps at their share screens; the share menu shows the real Telegram, WhatsApp and X icons. The sidebar's Full page button is gone (the panel's Maximize does the same).</div>
|
||||
|
|
@ -217,6 +217,20 @@
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Hermes for Android <span style="color:var(--acid)">0.3.1</span></h2>
|
||||
<div class="meta">Android 5.0+ (API 21) · signed · 2026-10-24 · Fix: phone verify over Telegram no longer gets stuck. Two live bugs. First, Android 11+ package visibility was blocking the tg:// deep link — the OS silently fell through to a browser (or threw) even with Telegram installed, so our startActivity could never actually dispatch /start to the bot; fixed by declaring the tg:// and https://t.me intents in the manifest <queries> block. Second, the https://t.me/<bot>?start=<nonce> URL only auto-sends /start on a brand-new chat with the bot — once you had opened the bot even once (common after a first verify attempt), the chat reopened with no Share-Phone button and no retry path; Hermes now prefers tg://resolve, which fires /start regardless of chat state. Polling also starts the moment a nonce is minted (not only on return from Telegram), honours the server's 10-minute nonce TTL instead of giving up at three, and the pane now carries Check-status-now / Reopen-Telegram-chat / Cancel-and-start-over controls so a stale verify can be unstuck without leaving the screen.</div>
|
||||
|
||||
<div class="file">
|
||||
<div class="n"><a href="https://dl.silentmode.st/hermes-v0.3.1.apk">hermes-v0.3.1.apk</a> — APK</div>
|
||||
<code>f3ebaea886cc363e131027514dd038343e522d31296b8dfdd46af1889c095637</code>
|
||||
</div>
|
||||
<div class="file">
|
||||
<div class="n">Signing certificate — SHA-256 (the same key signs every future release)</div>
|
||||
<code>b1e4685a7476fcbb3b53d807e298dea2ef2c7375f240cf04847d3d712cab95b7</code>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Hermes for Android <span style="color:var(--acid)">0.3.0</span></h2>
|
||||
<div class="meta">Android 5.0+ (API 21) · signed · 2026-10-24 · In-app auto-update. Hermes now polls dl.silentmode.st/releases-manifest.json on launch and on resume, and shows an update banner at the top of the chat list when a newer version is live. Tap Update → downloads the APK via the pinned client, SHA-256-verifies against the manifest field, then launches Android's package installer. Android refuses to install an APK signed by a different key than the running app, so a tampered manifest can at worst waste bandwidth. Same signing key as 0.2.2; installs over it. Requires the one-time Install-unknown-apps grant on first update, which Android shims via Settings.</div>
|
||||
|
|
@ -245,20 +259,6 @@
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Hermes for Android <span style="color:var(--acid)">0.2.1</span></h2>
|
||||
<div class="meta">Android 5.0+ (API 21) · signed · 2026-10-24 · Fix: real-time inbox delivery. 0.2.0 held a persistent inbox REQ at sign-in, but mobile WebSockets drop constantly (wifi/cellular transitions, OS backgrounding, keep-alive timeouts) and the REQ wasn't replayed on reconnect — the relay forgot our filter and inbound kind:1059 wraps stopped arriving until the next 15-min WorkManager poll or next outgoing send kicked a catch-up. RelayConnection now remembers active subscriptions and replays them on every onOpen, so a recipient sees messages the moment they land on the relay. Also pins the initial `since` to max(lastSeenAt, now - 7d), bounding the reconnect replay. Updates DeliveryPrefs.lastSeenAt on each decrypted wrap so background delivery stays in step.</div>
|
||||
|
||||
<div class="file">
|
||||
<div class="n"><a href="https://dl.silentmode.st/hermes-v0.2.1.apk">hermes-v0.2.1.apk</a> — APK</div>
|
||||
<code>014438c3c1a92dd0108d994ae411ed27bf2de58c735614498e86d11462066d61</code>
|
||||
</div>
|
||||
<div class="file">
|
||||
<div class="n">Signing certificate — SHA-256 (the same key signs every future release)</div>
|
||||
<code>b1e4685a7476fcbb3b53d807e298dea2ef2c7375f240cf04847d3d712cab95b7</code>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Hermes for Windows <span style="color:var(--acid)">0.1.0</span></h2>
|
||||
<div class="meta">Windows 64-bit · unsigned · 2026-10-23 · First desktop build: the Hermes messenger as a stand-alone Windows app (Tauri), byte-equal with the Theseus panel and the hermes.x web messenger. Sign in with a recovery phrase or create a new identity; same inbox on every surface.</div>
|
||||
|
|
|
|||
|
|
@ -110,6 +110,20 @@
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Ariadne for Android <span style="color:var(--acid)">0.53</span></h2>
|
||||
<div class="meta">Android 5.0+ (API 21) · self-signed release key · 2026-10-24 · Settings page is now a short menu of 11 labeled sections — one row-card per topic, with its icon and chevron. Tap a row to see that section on its own with a ‹ Settings back link; the URL hash remembers where you are, so toggles inside a section no longer bounce you back to the top. Same signing key; installs over 0.52.</div>
|
||||
|
||||
<div class="file">
|
||||
<div class="n"><a href="https://dl.silentmode.st/ariadne-v0.53.apk">ariadne-v0.53.apk</a> — APK</div>
|
||||
<code>6adedfd3f0e4c5742b79ac25f4575e03d2b0f8819785667e22f3a7d8eaad1c48</code>
|
||||
</div>
|
||||
<div class="file">
|
||||
<div class="n">Signing certificate — SHA-256 (the same key signs every future release)</div>
|
||||
<code>46ebbbe5dc73148d66410fd0337b1e6683472128c983e8e2578200b9e3ca548c</code>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Ariadne for Android <span style="color:var(--acid)">0.52</span></h2>
|
||||
<div class="meta">Android 5.0+ (API 21) · self-signed release key · 2026-10-24 · The updater now polls ariadne.x — manifest + APKs live in the s3://bns/ariadne/ bucket the on-chain record points to, routed through the public BNS gateway so a raw HTTPS client reaches them without the Ariadne resolver being up. Download page link also moved from silentmode.st to ariadne.x. Older clients keep polling the silentmode.st mirror; the manifest at both URLs stays in sync until the fleet has rolled over. Same signing key; installs over 0.51.</div>
|
||||
|
|
@ -138,20 +152,6 @@
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Ariadne for Android <span style="color:var(--acid)">0.50</span></h2>
|
||||
<div class="meta">Android 5.0+ (API 21) · self-signed release key · 2026-10-23 · New launcher icon — the laurel-crowned bust silhouette from the Ariadne.X brand kit, recoloured gold on navy. Replaces the figure-only mark; same signing key; installs over 0.49.</div>
|
||||
|
||||
<div class="file">
|
||||
<div class="n"><a href="https://dl.silentmode.st/ariadne-v0.50.apk">ariadne-v0.50.apk</a> — APK</div>
|
||||
<code>4ca980c58a21101f2b3b54a864a49f71912d424d07870778da21690efb45e35b</code>
|
||||
</div>
|
||||
<div class="file">
|
||||
<div class="n">Signing certificate — SHA-256 (the same key signs every future release)</div>
|
||||
<code>46ebbbe5dc73148d66410fd0337b1e6683472128c983e8e2578200b9e3ca548c</code>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Pithos <span style="color:var(--acid)">0.3.26</span></h2>
|
||||
<div class="meta">Windows 64-bit · unsigned · 2026-10-08 · In Theseus, Send on Telegram and Send on WhatsApp open Theseus's own Telegram and WhatsApp apps at their share screens; the share menu shows the real Telegram, WhatsApp and X icons. The sidebar's Full page button is gone (the panel's Maximize does the same).</div>
|
||||
|
|
@ -216,6 +216,20 @@
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Hermes for Android <span style="color:var(--acid)">0.3.1</span></h2>
|
||||
<div class="meta">Android 5.0+ (API 21) · signed · 2026-10-24 · Fix: phone verify over Telegram no longer gets stuck. Two live bugs. First, Android 11+ package visibility was blocking the tg:// deep link — the OS silently fell through to a browser (or threw) even with Telegram installed, so our startActivity could never actually dispatch /start to the bot; fixed by declaring the tg:// and https://t.me intents in the manifest <queries> block. Second, the https://t.me/<bot>?start=<nonce> URL only auto-sends /start on a brand-new chat with the bot — once you had opened the bot even once (common after a first verify attempt), the chat reopened with no Share-Phone button and no retry path; Hermes now prefers tg://resolve, which fires /start regardless of chat state. Polling also starts the moment a nonce is minted (not only on return from Telegram), honours the server's 10-minute nonce TTL instead of giving up at three, and the pane now carries Check-status-now / Reopen-Telegram-chat / Cancel-and-start-over controls so a stale verify can be unstuck without leaving the screen.</div>
|
||||
|
||||
<div class="file">
|
||||
<div class="n"><a href="https://dl.silentmode.st/hermes-v0.3.1.apk">hermes-v0.3.1.apk</a> — APK</div>
|
||||
<code>f3ebaea886cc363e131027514dd038343e522d31296b8dfdd46af1889c095637</code>
|
||||
</div>
|
||||
<div class="file">
|
||||
<div class="n">Signing certificate — SHA-256 (the same key signs every future release)</div>
|
||||
<code>b1e4685a7476fcbb3b53d807e298dea2ef2c7375f240cf04847d3d712cab95b7</code>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Hermes for Android <span style="color:var(--acid)">0.3.0</span></h2>
|
||||
<div class="meta">Android 5.0+ (API 21) · signed · 2026-10-24 · In-app auto-update. Hermes now polls dl.silentmode.st/releases-manifest.json on launch and on resume, and shows an update banner at the top of the chat list when a newer version is live. Tap Update → downloads the APK via the pinned client, SHA-256-verifies against the manifest field, then launches Android's package installer. Android refuses to install an APK signed by a different key than the running app, so a tampered manifest can at worst waste bandwidth. Same signing key as 0.2.2; installs over it. Requires the one-time Install-unknown-apps grant on first update, which Android shims via Settings.</div>
|
||||
|
|
@ -244,20 +258,6 @@
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Hermes for Android <span style="color:var(--acid)">0.2.1</span></h2>
|
||||
<div class="meta">Android 5.0+ (API 21) · signed · 2026-10-24 · Fix: real-time inbox delivery. 0.2.0 held a persistent inbox REQ at sign-in, but mobile WebSockets drop constantly (wifi/cellular transitions, OS backgrounding, keep-alive timeouts) and the REQ wasn't replayed on reconnect — the relay forgot our filter and inbound kind:1059 wraps stopped arriving until the next 15-min WorkManager poll or next outgoing send kicked a catch-up. RelayConnection now remembers active subscriptions and replays them on every onOpen, so a recipient sees messages the moment they land on the relay. Also pins the initial `since` to max(lastSeenAt, now - 7d), bounding the reconnect replay. Updates DeliveryPrefs.lastSeenAt on each decrypted wrap so background delivery stays in step.</div>
|
||||
|
||||
<div class="file">
|
||||
<div class="n"><a href="https://dl.silentmode.st/hermes-v0.2.1.apk">hermes-v0.2.1.apk</a> — APK</div>
|
||||
<code>014438c3c1a92dd0108d994ae411ed27bf2de58c735614498e86d11462066d61</code>
|
||||
</div>
|
||||
<div class="file">
|
||||
<div class="n">Signing certificate — SHA-256 (the same key signs every future release)</div>
|
||||
<code>b1e4685a7476fcbb3b53d807e298dea2ef2c7375f240cf04847d3d712cab95b7</code>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="rel">
|
||||
<h2>Hermes for Windows <span style="color:var(--acid)">0.1.0</span></h2>
|
||||
<div class="meta">Windows 64-bit · unsigned · 2026-10-23 · First desktop build: the Hermes messenger as a stand-alone Windows app (Tauri), byte-equal with the Theseus panel and the hermes.x web messenger. Sign in with a recovery phrase or create a new identity; same inbox on every surface.</div>
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue