## Amber 6.1.0-pre2 - Better layout when connecting a new app - Fix some reported crashes - Fix signer dialog not closing after accepting a bunker request - Show name and npub when showing your account - Add a select/deselect all option in the permissions screen when connecting a new app - Show a invalid request screen when receiving a invalid request - Preview missing translation report before sending it - Add a rate limiting for intents based on app/type/event kind (rate limiting only applies to apps that don't implement sending multiple requests at once) - Some optimizations when accepting/rejecting intent requests - Added a stop service in the notification, this force closes the app and you have to manually open it again before using bunker applications - Added a option to disable the service start on boot - Only start the profile subscription for the current account - Always return hex key when logging in to an app to comply with nip 55 - Added a close button in the empty requests screen - Added loading state to the report screens - Support for beta releases for the auto updater - Add a reset button for bunkers - Fix a connection issue when connecting to a new bunker by @Alex Gleason - Fix app starting on boot when not enabled Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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.1.0-pre2) 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.1.0-pre2.txt` and `manifest-v6.1.0-pre2.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.1.0-pre2.txt.sig manifest-v6.1.0-pre2.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.1.0-pre2.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.

## Amber 6.1.0-pre1 - Better layout when connecting a new app - Fix some reported crashes - Fix signer dialog not closing after accepting a bunker request - Show name and npub when showing your account - Add a select/deselect all option in the permissions screen when connecting a new app - Show a invalid request screen when receiving a invalid request - Preview missing translation report before sending it - Add a rate limiting for intents based on app/type/event kind (rate limiting only applies to apps that don't implement sending multiple requests at once) - Some optimizations when accepting/rejecting intent requests - Added a stop service in the notification, this force closes the app and you have to manually open it again before using bunker applications - Added a option to disable the service start on boot - Only start the profile subscription for the current account - Always return hex key when logging in to an app to comply with nip 55 Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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.1.0-pre1) 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.1.0-pre1.txt` and `manifest-v6.1.0-pre1.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.1.0-pre1.txt.sig manifest-v6.1.0-pre1.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.1.0-pre1.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.

## Amber 6.0.3 - Fix racing condition when receiving intents - Upgrade gradle and agp - Add account index option when using seed words - Fix relay reconnection on startup if the relay is offline - Add missing periodic worker for app updates - Check for empty request ids when receiving intents Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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.0.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.0.3.txt` and `manifest-v6.0.3.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.0.3.txt.sig manifest-v6.0.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.0.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.

## Amber 6.0.2 - Fix racing condition when receiving intents - Upgrade gradle and agp - Add account index option when using seed words - Fix relay reconnection on startup if the relay is offline - Add missing periodic worker for app updates Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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.0.2) 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.0.2.txt` and `manifest-v6.0.2.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.0.2.txt.sig manifest-v6.0.2.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.0.2.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.

## Amber 6.0.1 - Fix missing event validation when checking for app updates and profile events - Fix racing condition when receiving intents - Fix subscriptions never closing when removing an app - Remove richtext dependency - Update Quartz library to 1.08.0 - Add two new backup options, webdav and share to google drive - Implement exponential backoff for relay reconnections Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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.0.1) 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.0.1.txt` and `manifest-v6.0.1.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.0.1.txt.sig manifest-v6.0.1.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.0.1.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.

## Amber 6.0.0 - Add per-connection signing keys for NIP-46 bunker protocol - Add NIP-42 relay auth whitelist settings - Add mnemonic recovery phrase login support - Fix a crash when receiving duplicated events - Optimize performance in content resolvers, intents and activity screen - Optimized logs and activities to reduce the size of the database - Fix a crash when pasting from clipboard - Make relays notifications minimized by default - Fix a database migration error - Warn the user when their device has a broken KeyStore - Add a self updater Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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.0.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.0.0.txt` and `manifest-v6.0.0.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.0.0.txt.sig manifest-v6.0.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.0.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.

## Amber 6.0.0-pre1 - Add per-connection signing keys for NIP-46 bunker protocol - Add NIP-42 relay auth whitelist settings - Add mnemonic recovery phrase login screen - Fix a crash when receiving duplicated events - Optimize performance in content resolvers, intents and activity screen - Optimized logs and activities to reduce the size of the database Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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.0.0-pre1) 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.0.0-pre1.txt` and `manifest-v6.0.0-pre1.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.0.0-pre1.txt.sig manifest-v6.0.0-pre1.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.0.0-pre1.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.

## Amber 5.0.4 - Do not start service, tor or notifications when using the offline version - Do not re-add bunker requests when failed to send response - Better performance when receiving multiple requests - Add a 30 second timeout for profile subscriptions - Remove the tabs from the connect screen - Fix rejection not respecting the scoped encrypt/decrypt - Show alt tags when there's no translation for a event kind - use a boolean for the intent rejection - Fix the accept/reject button not showing when scanning a nostrconnect qrcode Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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/v5.0.4) 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-v5.0.4.txt` and `manifest-v5.0.4.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v5.0.4.txt.sig manifest-v5.0.4.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-v5.0.4.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.

## Amber 5.0.2 - Do not start service, tor or notifications when using the offline version - Do not re-add bunker requests when failed to send response - Better performance when receiving multiple requests - Add a 30 second timeout for profile subscriptions - Remove the tabs from the connect screen - Fix rejection not respecting the scoped encrypt/decrypt - Show alt tags when there's no translation for a event kind - use a boolean for the intent rejection Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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/v5.0.2) 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-v5.0.2.txt` and `manifest-v5.0.2.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v5.0.2.txt.sig manifest-v5.0.2.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-v5.0.2.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.

## Amber 5.0.1 - Always remove internet permissions from offline build to avoid dependencies adding them - Add a CI check for the internet permissions in the offline build - Option for built in tor - Search the content in the activities screen - Granular encryption/decryption based on data type - Migrate PIN storage from SharedPreferences to encrypted DataStore - Fix crash on offline build - Show the crash report content before sending Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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/v5.0.1) 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-v5.0.1.txt` and `manifest-v5.0.1.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v5.0.1.txt.sig manifest-v5.0.1.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-v5.0.1.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.

## Amber 5.0.0 - Always remove internet permissions from offline build to avoid dependencies adding them - Add a CI check for the internet permissions in the offline build - Option for built in tor - Search the content in the activities screen - Granular encryption/decryption based on data type - Migrate PIN storage from SharedPreferences to encrypted DataStore Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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/v5.0.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-v5.0.0.txt` and `manifest-v5.0.0.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v5.0.0.txt.sig manifest-v5.0.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-v5.0.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.

## Amber 4.1.3 - Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me - Better relay notification text - Fix relay icon when more than 10 relays - Hide icon and relay notification if not using apps that connect to relays - Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec - Do not use strongBox when it's a mediatek device, it's breaking all the time - Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press - Remove relay.nsec.app from defaults (it's not working properly sometimes) - Close profile subscriptions once receiving EOSE from relays - Fix icon size and themed icon - Show the account that is signing the event - Show a button to report unknown event kinds - Better relay connection management - Refactor start service - Use bottom sheet for requests instead of showing the full application - Display the "Sign as" widget in the multi event screen - Decrease the timeout of sending response to relays - Show request content in the activities screen - Client auth permissions by relay - Fix a crash when loading profile image - Do not group events when receiving multiple events Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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/v4.1.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-v4.1.3.txt` and `manifest-v4.1.3.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v4.1.3.txt.sig manifest-v4.1.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-v4.1.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.

## Amber 4.1.3-pre4 - Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me - Better relay notification text - Fix relay icon when more than 10 relays - Hide icon and relay notification if not using apps that connect to relays - Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec - Do not use strongBox when it's a mediatek device, it's breaking all the time - Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press - Remove relay.nsec.app from defaults (it's not working properly sometimes) - Close profile subscriptions once receiving EOSE from relays - Fix icon size and themed icon - Show the account that is signing the event - Show a button to report unknown event kinds - Better relay connection management - Refactor start service - Use bottom sheet for requests instead of showing the full application - Display the "Sign as" widget in the multi event screen - Decrease the timeout of sending response to relays - Show rquest content in the activities screen - Client auth permissions by relay - Fix a crash when loading profile image - Do not group events when receiving multiple events Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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/v4.1.3-pre4) 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-v4.1.3-pre4.txt` and `manifest-v4.1.3-pre4.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v4.1.3-pre4.txt.sig manifest-v4.1.3-pre4.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-v4.1.3-pre4.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.

## Amber 4.1.3-pre3 - Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me - Better relay notification text - Fix relay icon when more than 10 relays - Hide icon and relay notification if not using apps that connect to relays - Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec - Do not use strongBox when it's a mediatek device, it's breaking all the time - Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press - Remove relay.nsec.app from defaults (it's not working properly sometimes) - Close profile subscriptions once receiving EOSE from relays - Fix icon size and themed icon - Show the account that is signing the event - Show a button to report unknown event kinds - Better relay connection management - Refactor start service - Use bottom sheet for requests instead of showing the full application - Display the "Sign as" widget in the multi event screen - Decrease the timeout of sending response to relays - Show rquest content in the activities screen - Client auth permissions by relay - Fix a crash when loading profile image Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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/v4.1.3-pre3) 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-v4.1.3-pre3.txt` and `manifest-v4.1.3-pre3.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v4.1.3-pre3.txt.sig manifest-v4.1.3-pre3.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-v4.1.3-pre3.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.

## Amber 4.1.3-pre2 - Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me - Better relay notification text - Fix relay icon when more than 10 relays - Hide icon and relay notification if not using apps that connect to relays - Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec - Do not use strongBox when it's a mediatek device, it's breaking all the time - Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press - Remove relay.nsec.app from defaults (it's not working properly sometimes) - Close profile subscriptions once receiving EOSE from relays - Fix icon size and themed icon - Show the account that is signing the event - Show a button to report unknown event kinds - Better relay connection management - Refactor start service - Use bottom sheet for requests instead of showing the full application - Display the "Sign as" widget in the multi event screen - Decrease the timeout of sending response to relays Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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/v4.1.3-pre2) 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-v4.1.3-pre2.txt` and `manifest-v4.1.3-pre2.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v4.1.3-pre2.txt.sig manifest-v4.1.3-pre2.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-v4.1.3-pre2.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.

## Amber 4.1.3-pre1 - Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me - Better relay notification text - Fix relay icon when more than 10 relays - Hide icon and relay notification if not using apps that connect to relays - Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec - Do not use strongBox when it's a mediatek device, it's breaking all the time - Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press - Remove relay.nsec.app from defaults (it's not working properly sometimes) - Close profile subscriptions once receiving EOSE from relays - Fix icon size and themed icon Download it with [Zapstore](

Zapstore

App Details — Zapstore

Discover apps on Nostr. Open source, decentralized app store.

[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/v4.1.3-pre1) 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-v4.1.3-pre1.txt` and `manifest-v4.1.3-pre1.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v4.1.3-pre1.txt.sig manifest-v4.1.3-pre1.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-v4.1.3-pre1.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.

## Amber 4.1.2 - Fix some missing Relay trusted score in some screens - Move some components to it's own file - Use full uuid for bunker secrets - Remove some unused dependencies - Migrate from LiveData to Flow in the account Model - Upgrade to gradle plugin 9 - Fix json parsing error for encrypt/decrypt requests when they are not nostr events - Fix a crash when receiving a auth event without relay tags Download it with [zapstore.dev](https://zapstore.dev/download), [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/v4.1.2) 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-v4.1.2.txt` and `manifest-v4.1.2.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v4.1.2.txt.sig manifest-v4.1.2.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-v4.1.2.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.

## Amber 4.1.2-pre1 - Fix some missing Relay trusted score in some screens - Move some components to it's own file - Use full uuid for bunker secrets - Remove some unused dependencies - Migrate from LiveData to Flow in the account Model - Upgrade to gradle plugin 9 - Fix json parsing error for encrypt/decrypt requests when they are not nostr events Download it with [zapstore.dev](https://zapstore.dev/download), [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/v4.1.2-pre1) 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-v4.1.2-pre1.txt` and `manifest-v4.1.2-pre1.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v4.1.2-pre1.txt.sig manifest-v4.1.2-pre1.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-v4.1.2-pre1.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.

## Amber 4.1.1 - New ui for login, events and permissions screen - Refactor relay counters to use the updated method from quartz library - Fix relay connection not closing when trying to add a unsupported relay - Expose datastore errors - Fix connection not being deleted when it fails when using bunker - Add a loading indicator when login in - Let the app crash when it fails to read the intent - Use application wide scope for the datastore - Remove migration code from old encrypted shared preferences - Throw a error if could not find the private keys inside the keystore - Cache keystore and signer (some 'old' devices are taking 20+ seconds to load the keystore) - Relay trusted score by @Geektoshi - Verify if account exists before trying to load the keys - Support for `switch_relays` method Download it with [zapstore.dev](https://zapstore.dev/download), [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/v4.1.1) 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-v4.1.1.txt` and `manifest-v4.1.1.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v4.1.1.txt.sig manifest-v4.1.1.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-v4.1.1.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.

## Amber 4.1.0 - New ui for login, events and permissions screen - Refactor relay counters to use the updated method from quartz library - Fix relay connection not closing when trying to add a unsupported relay - Expose datastore errors - Fix connection not being deleted when it fails when using bunker - Add a loading indicator when login in - Let the app crash when it fails to read the intent - Use application wide scope for the datastore - Remove migration code from old encrypted shared preferences - Throw a error if could not find the private keys inside the keystore - Cache keystore and signer (some 'old' devices are taking 20+ seconds to load the keystore) Download it with [zapstore.dev](https://zapstore.dev/download), [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/v4.1.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-v4.1.0.txt` and `manifest-v4.1.0.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v4.1.0.txt.sig manifest-v4.1.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-v4.1.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.