fef4e6d347
fc7629b landed in the 0.3.28 build but the release-notes text still read as "three changes since 0.3.27". Adding it as (4) so the change is visible on silentmode.st/releases/ once the site scp goes out. Binaries unchanged (same 5d15508b / a5d346b9 hashes).
51 lines
3.4 KiB
JSON
51 lines
3.4 KiB
JSON
{
|
||
"schema": "silentmode-releases/2",
|
||
"updated": "2026-09-08",
|
||
"mirrors": [
|
||
"https://dl.silentmode.st/"
|
||
],
|
||
"releases": [
|
||
{
|
||
"id": "ariadne-resolver",
|
||
"product": "Ariadne Resolver (Windows)",
|
||
"version": "0.1.1",
|
||
"date": "2026-09-08",
|
||
"platform": "win-x64",
|
||
"signed": false,
|
||
"signingAuthority": null,
|
||
"changes": "NRPT rules and CA constraints now driven by silentmode.st /api/tlds (HTTPS) with electrum/config fallback -- silent installs no longer break when WSS fails. install.ps1 writes a persistent transcript to C:\\ProgramData\\Ariadne\\install.log and a separate install-error.log on any uncaught exception, so /VERYSILENT failures leave forensics. Inno's own log is copied there too. Fixes the class of bug where the resolver appeared installed but the BNS Resolver Daemon scheduled task was never registered.",
|
||
"files": {
|
||
"AriadneResolver-Setup-0.1.1.exe": "be1fa8841919b321841d90f8147abe1b1d7604fe7fff6c2e271dc47c4c24a2b6"
|
||
}
|
||
},
|
||
{
|
||
"id": "ariadne-android",
|
||
"product": "Ariadne for Android",
|
||
"version": "0.11",
|
||
"date": "2026-08-30",
|
||
"platform": "android",
|
||
"minSdk": 21,
|
||
"signed": true,
|
||
"signingAuthority": null,
|
||
"signingCertSha256": "46ebbbe5dc73148d66410fd0337b1e6683472128c983e8e2578200b9e3ca548c",
|
||
"changes": "Adds a Sia-mirror pull path alongside the APK-bundled starter (0.10). On boot the app fires a background HTTP GET for dl.silentmode.st/bns-name-index.json — the operator's latest published BNS snapshot in the interpreted-index format Bns.saveDisk reads. On any subsequent cold start after a release, the browser converges on the current chain state with one HTTP call instead of a full electrum walk. Multi-source: bundled + CDN + on-device electrum + optional Argus indexer, all racing in parallel; whichever gives a fresh answer first wins.",
|
||
"files": {
|
||
"ariadne-v0.11.apk": "03c95832c16cc4763acaadbf328caa7d4bd05fc7c2994f6997a79cc6890bca44"
|
||
}
|
||
},
|
||
{
|
||
"id": "theseus-navigator",
|
||
"product": "Theseus Navigator",
|
||
"version": "0.3.28",
|
||
"date": "2026-09-08",
|
||
"platform": "win-x64",
|
||
"signed": false,
|
||
"signingAuthority": null,
|
||
"changes": "Four changes since 0.3.27. (1) Aegis (built-in wallet) gains its own update card in Settings > General, right beside Ariadne. Signed OTA updates ship without a Theseus release — Check for updates hits the same signed endpoint the boot timer uses; Restart to apply shows once a staged version is ready. (2) DevTools (F12 / Ctrl+Shift+I) opens docked to the right of the tab instead of popping a detached window, matching stock Chrome. (3) Search-engine favicons in Settings > Search now use Google's /s2/favicons service — the DuckDuckGo ip3 source returned 404 for enough hosts (Brave, Bing, Yandex, etc.) that half the list was falling through to the emoji placeholder. (4) Settings > Extensions > Check for updates now shows per-add-on status (up to date / fetch failed / signature invalid / staged etc.) instead of one indistinguishable 'up to date' line — a silent DNS or sig-verify failure will no longer look like success. Everything from 0.3.22 – 0.3.27 rides along.",
|
||
"files": {
|
||
"TheseusNavigator-Setup-0.3.28.exe": "5d15508bba929f1f074c052ac933863eadf6eb8e56984ebd5a1af75e80626643",
|
||
"TheseusNavigator-0.3.28-portable.exe": "a5d346b97f5a13d85fa3bd301a72075ddb82fe636d7b1a51840ffd5a16d879f4"
|
||
}
|
||
}
|
||
]
|
||
}
|