vjrj
954dc2caae
All checks were successful
ci / analyze (push) Successful in 1m7s
ci / test-commons-core (push) Successful in 36s
ci / test-app-seeds (push) Successful in 5m48s
site / deploy (push) Successful in 35s
release / analyze (push) Successful in 1m7s
release / test-commons-core (push) Successful in 44s
release / test-app-seeds (push) Successful in 6m26s
release / play (push) Successful in 13m5s
release / fdroid_reference_armeabi_v7a (push) Successful in 23m4s
release / fdroid_reference_arm64_v8a (push) Successful in 23m23s
release / fdroid_reference_x86_64 (push) Successful in 23m13s
The store listing claimed "No account, no server, no trackers" while the app was dialling four relays at launch. The app side is fixed; this is the half a reader sees. - Store description, both locales: the false line is gone, and a new "Sharing needs the internet" block names relay.comunes.org (ours), nos.lol, relay.damus.io and relay.primal.net, says when Tane talks to them, what they can see (a key and an IP — no name, no account), and where to switch any or all of them off, or point Tane at your own. Deliberately plain: no protocol names, no jargon. The audience is gardeners; the technical detail belongs in the F-Droid thread. - The same correction on the landing page (feature card, FAQ, status). - 0.1.16+18, so the F-Droid recipe's versionCodes become 181/182/183. F-Droid reads fastlane metadata from the checkout of the newest built version, so the description only reaches it via a new release. The recipe mirror's `commit:` still points at v0.1.15 — it needs a hash that does not exist yet, and is synced here and in the fdroiddata fork once v0.1.16 is tagged. |
||
|---|---|---|
| .. | ||
| 1.txt | ||
| 3.txt | ||
| 4.txt | ||
| 18.txt | ||