## Amber 4.0.3 - Fix close application logic for bunkers - Add a Export/Import accounts method by - Separate relay reqs per account - Update relay reqs when adding an account - New encryption/decryption ui - Support for ping requests when using bunker - Fix encryption type by - Separate logs and history tables in it's own databases - Add crash reporting - Try to get the saved account in the get public key of the content provider - Use quartz from maven - Save logs when there's a error using content provider - Add a text to the relays page floating button - Show the relays used by apps 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.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-v4.0.3.txt` and `manifest-v4.0.3.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v4.0.3.txt.sig manifest-v4.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 " ``` 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.0.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.0.3-pre2 - Fix close application logic for bunkers - Add a Export/Import accounts method by - Separate relay reqs per account - Update relay reqs when adding an account - New encryption/decryption ui - Support for ping requests when using bunker - Fix encryption type by - Separate logs and history tables in it's own databases - Add crash reporting - Try to get the saved account in the get public key of the content provider - Use quartz from maven - Save logs when there's a error using content provider - Add a text to the relays page floating button - Show the relays used by apps - Fix export account - Clear account cache on logout - Only load private keys on demand - Remove nip11 fetch when adding a new relay since we don't verify anything anymore - Update relay requests when deleting an app 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.0.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.0.3-pre2.txt` and `manifest-v4.0.3-pre2.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v4.0.3-pre2.txt.sig manifest-v4.0.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.0.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.

jumble.social

Added it

Sure, I'll add it later