## Amber 6.4.0 - Redesign the multi-request approval screen with explicit Approve/Deny toggles per request and per group, replacing the select-and-confirm flow, with proper error responses for denied bunker requests - Add support for 113 more event kinds with localized labels across all shipped locales, including the Concord kinds, NIP-51 git repository bookmarks and NIP-53 room presence - Add light/dark Compose previews for the multi-event approval screens - Ignore platform finalizer-watchdog TimeoutExceptions in crash reports - Fix a NegativeArraySizeException crash in relay subscriptions by guarding shared maps for concurrent access - Translate the new approval strings (approve, confirm, remember my choice for) in all supported locales - Update translations Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.4.0) If you like my work consider making a [donation](https://greenart7c3.com) ## Verifying the release In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.4.0.txt` and `manifest-v6.4.0.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.4.0.txt.sig manifest-v6.4.0.txt ``` You should see the following if the verification was successful: ``` bash gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03 gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>" ``` That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes: ``` bash cat manifest-v6.4.0.txt ``` One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly. ## Older versions Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

# Changelog ## Amber 6.3.0 - Group multi-request approval lists by type and kind, with collapsible groups and per-group remember and scope options - Only use the fullscreen layout when there is a single bunker request - Add support for Expert List (kind 12022) and Expert Pack (kind 32022) events - Add a privacy mode setting to disable logs and activity stats - Add a setting to disable relay trust scores - Add a restart action and live status to the built-in Tor notification - Fetch the user's NIP-65 relay list before fetching profile metadata - Remove relay.damus.io from the default relay lists - Fix the event date shown as Jan 1970 in the Show Details modals - Fix all Android Lint warnings and enforce lint in the git hooks - Upgrade Gradle to 9.6.1 and AGP to 9.3.0 - Move older release notes to per-version files under docs/changelogs - Update translations Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.3.0) If you like my work consider making a [donation](https://greenart7c3.com) ## Verifying the release In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.3.0.txt` and `manifest-v6.3.0.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.3.0.txt.sig manifest-v6.3.0.txt ``` You should see the following if the verification was successful: ``` bash gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03 gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>" ``` That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes: ``` bash cat manifest-v6.3.0.txt ``` One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly. ## Older versions Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

## Amber 6.2.3 - Add a configurable profile fetch interval setting with never/always options - Show a profile picture in the account switch bottom sheet - Scope profile subscriptions by the current account, driven by composables - Add error handling to bunker permission parsing - Trim the shipped languages to the curated set of locales - Set the benchmark build app name to "Amber Benchmark" - Fix a StrictMode DiskReadViolation in Coil onSuccess logging - Load the account off the main thread to fix a StrictMode keystore violation - Read account name and picture off the main thread in the account switch sheet - Avoid eager KeyPair() on the main thread in the login/signup screens - Fix the settings section header contrast in the light theme - Fix an unescaped apostrophe in the Turkish profile fetch interval string - Update translations Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.2.3) If you like my work consider making a [donation](https://greenart7c3.com) ## Verifying the release In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.2.3.txt` and `manifest-v6.2.3.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.2.3.txt.sig manifest-v6.2.3.txt ``` You should see the following if the verification was successful: ``` bash gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03 gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>" ``` That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes: ``` bash cat manifest-v6.2.3.txt ``` One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.