## 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](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [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 " ``` 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 ` 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](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [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 " ``` 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 ` 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](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [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 " ``` 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 ` 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](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [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 " ``` 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 ` 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](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [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 " ``` 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 ` 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](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [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 " ``` 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 ` 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](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [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 " ``` 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 ` 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](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [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 " ``` 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 ` 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.