Release v2.0.5

Amber 2.0.5

• If you are coming from version 1.3.7 or lower you will need to first backup your accounts, uninstall the old version and install the new version
• Fix nip 04 decryption for web applications

Download it with zap.store, 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-v2.0.5.txt and manifest-v2.0.5.txt.sig are in the current directory) with:

gpg --verify manifest-v2.0.5.txt.sig manifest-v2.0.5.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 <[email protected]>"

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-v2.0.5.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.

Release v2.0.4

Amber 2.0.4

• If you are coming from version 1.3.7 or lower you will need to first backup your accounts, uninstall the old version and install the new version
• Update dependencies
• When using a native app always show the package id
• When reading a QrCode in the login screen make it lowercase

Download it with zap.store, 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-v2.0.4.txt and manifest-v2.0.4.txt.sig are in the current directory) with:

gpg --verify manifest-v2.0.4.txt.sig manifest-v2.0.4.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 <[email protected]>"

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-v2.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.

Release v2.0.3

Amber 2.0.3

• If you are coming from version 1.3.7 or lower you will need to first backup your accounts, uninstall the old version and install the new version
• Fix crash when signing multiple events

Download it with zap.store, 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-v2.0.3.txt and manifest-v2.0.3.txt.sig are in the current directory) with:

gpg --verify manifest-v2.0.3.txt.sig manifest-v2.0.3.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 <[email protected]>"

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-v2.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.

Release v2.0.2

Amber 2.0.2

• If you are coming from version 1.3.7 or lower you will need to first backup your accounts, uninstall the old version and install the new version
• Redesign the multi event screen

Download it with zap.store, 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-v2.0.2.txt and manifest-v2.0.2.txt.sig are in the current directory) with:

gpg --verify manifest-v2.0.2.txt.sig manifest-v2.0.2.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 <[email protected]>"

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-v2.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.

Release v2.0.1

Amber 2.0.1

• New sign keys, to use this version you will need to first backup your accounts, uninstall the old version and install the new version
• When you not configured a notification type Amber will ask you to configure and default to direct connection to relays
• Check if is a valid relay before adding it when changing the default relays or adding a relay to a application

Download it with zap.store, 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-v2.0.1.txt and manifest-v2.0.1.txt.sig are in the current directory) with:

gpg --verify manifest-v2.0.1.txt.sig manifest-v2.0.1.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 <[email protected]>"

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-v2.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.

Release v2.0.0

Amber 2.0.0

• New sign keys, to use this version you will need to first backup your accounts, uninstall the old version and install the new version
• When you not configured a notification type Amber will ask you to configure and default to direct connection to relays
• Check if is a valid relay before adding it when changing the default relays or adding a relay to a application

Download it with zap.store, 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-v2.0.0.txt and manifest-v2.0.0.txt.sig are in the current directory) with:

gpg --verify manifest-v2.0.0.txt.sig manifest-v2.0.0.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 <[email protected]>"

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-v2.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.

Release v1.3.7

Amber 1.3.7

• Fix connection to the push notification server when using gCompat UP distributor
• Added more event descriptions
• Updated dependencies

Download it with zap.store, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

Release v1.3.6

Amber 1.3.6

• More connection fixes
• Don't register to the push server when using direct connection
• if theres no relay use the default relays

Download it with zap.store, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

Release v1.3.5

Amber 1.3.5

• Fix some connection issues

Download it with zap.store, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

Release v1.3.4

Amber 1.3.4

• Fix nostrconnect uri parser
• Change foreground service type
• Support for permissions when using nostrconnect uri
• UI changes when receiving multiple events

Download it with zap.store, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation