## 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 - 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 " ``` 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 ` 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.
