From 888013b296f44fcae54776b08df907e22275ba96 Mon Sep 17 00:00:00 2001 From: Local Dev Date: Mon, 28 Sep 2026 02:02:21 +0200 Subject: [PATCH] =?UTF-8?q?site:=20Ariadne=20for=20Android=200.20=20?= =?UTF-8?q?=E2=80=94=20manifest=20and=20releases=20page?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- releases-manifest.json | 10 +++++----- releases/index.html | 8 ++++---- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/releases-manifest.json b/releases-manifest.json index 1d5c56b..e9154df 100644 --- a/releases-manifest.json +++ b/releases-manifest.json @@ -1,6 +1,6 @@ { "schema": "silentmode-releases/2", - "updated": "2026-09-27", + "updated": "2026-09-28", "mirrors": [ "https://dl.silentmode.st/" ], @@ -35,16 +35,16 @@ { "id": "ariadne-android", "product": "Ariadne for Android", - "version": "0.19", - "date": "2026-09-19", + "version": "0.20", + "date": "2026-09-28", "platform": "android", "minSdk": 21, "signed": true, "signingAuthority": null, "signingCertSha256": "46ebbbe5dc73148d66410fd0337b1e6683472128c983e8e2578200b9e3ca548c", - "changes": "Consensus fix: the on-device index now applies the TLD co-sign rule. A name registered under a TLD whose owner set policy \"cosign\" or switched the TLD off (hidden) only counts when the registration transaction also carries the TLD's own certificate, exactly as the gateway, Theseus and the desktop resolver decide it, so every client agrees on which names exist. The index reads the per-TLD certificate registry and its policy history from the TLD beacon at build time; if that beacon cannot be reached it keeps the previous behaviour instead of returning an empty index. No UI changes.", + "changes": "Every live BNS TLD is claimed by the on-device resolver. The app took its TLD list from the registry's legacy advertised set (nine TLDs), so a name under a newer TLD was only intercepted once it had turned up in the local index; the app now reads the registry's routable list (every TLD on the public listing, 24 today), and ships a bootstrap list matching it for cold start. The cold-start snapshot it pulls from the CDN is now refreshed every ten minutes from the gateway's index instead of by hand, so a fresh install sees names registered minutes ago rather than weeks. Same signing key; installs over 0.19.", "files": { - "ariadne-v0.19.apk": "d2f4ad359e7ac36c1d0729100aef613be968cd17b153e94e124f8500fcbfc711" + "ariadne-v0.20.apk": "e7362e356de14f010646f3c60908ccd4bbd8030914f7e6a5dc2722d9dcf5e51e" } }, { diff --git a/releases/index.html b/releases/index.html index f4dcc64..4119a1c 100644 --- a/releases/index.html +++ b/releases/index.html @@ -82,12 +82,12 @@
-

Ariadne for Android 0.19

-
Android 5.0+ (API 21) · self-signed release key · 2026-09-19 · 0.19 — co-sign rule — Consensus fix: the on-device index now applies the TLD co-sign rule. A name registered under a TLD whose owner set policy "cosign" or switched the TLD off (hidden) only counts when the registration transaction also carries the TLD's own certificate, exactly as the gateway, Theseus and the desktop resolver decide it, so every client agrees on which names exist. The index reads the per-TLD certificate registry and its policy history from the TLD beacon at build time; if that beacon cannot be reached it keeps the previous behaviour instead of returning an empty index. No UI changes.
+

Ariadne for Android 0.20

+
Android 5.0+ (API 21) · self-signed release key · 2026-09-28 · 0.20 — every live TLD, fresh snapshot — Every live BNS TLD is claimed by the on-device resolver. The app took its TLD list from the registry's legacy advertised set (nine TLDs), so a name under a newer TLD was only intercepted once it had turned up in the local index; the app now reads the registry's routable list (every TLD on the public listing, 24 today), and ships a bootstrap list matching it for cold start. The cold-start snapshot it pulls from the CDN is now refreshed every ten minutes from the gateway's index instead of by hand, so a fresh install sees names registered minutes ago rather than weeks. Same signing key; installs over 0.19.
- - d2f4ad359e7ac36c1d0729100aef613be968cd17b153e94e124f8500fcbfc711 + + e7362e356de14f010646f3c60908ccd4bbd8030914f7e6a5dc2722d9dcf5e51e
Signing certificate — SHA-256 (the same key signs every future release)