greenart7c3/Amber v4.1.3-pre1

Release v4.1.3-pre1

on GitHub

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, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

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:

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:

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:

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:

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.