Releases · greenart7c3/Amber

Amber 4.0.6

Remove get_public_key from content provider
Handle parsing errors when trying to decrypt content to show the content for the user
Fix a crash on edit app the permission screen
Add a cache to the signer to improve performance
Use finishAndRemoveTask instead of finish
Fix screen recomposition
Fix crash when reading a invalid nostrconnect URI
Retry sending connect event on failure when adding a relay

Download it with zapstore.dev, 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.0.6.txt and manifest-v4.0.6.txt.sig are in the current directory) with:

gpg --verify manifest-v4.0.6.txt.sig manifest-v4.0.6.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.0.6.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.

Amber 4.0.6-pre2

Remove get_public_key from content provider
Handle parsing errors when trying to decrypt content to show the content for the user
Fix a crash on edit app the permission screen
Add a cache to the signer to improve performance
Use finishAndRemoveTask instead of finish
Fix screen recomposition

Download it with zapstore.dev, 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.0.6-pre2.txt and manifest-v4.0.6-pre2.txt.sig are in the current directory) with:

gpg --verify manifest-v4.0.6-pre2.txt.sig manifest-v4.0.6-pre2.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.0.6-pre2.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.

Amber 4.0.6-pre1

Remove get_public_key from content provider
Handle parsing errors when trying to decrypt content to show the content for the user
Fix a crash on edit app the permission screen
Add a cache to the signer to improve performance
Use finishAndRemoveTask instead of finish

Download it with zapstore.dev, 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.0.6-pre1.txt and manifest-v4.0.6-pre1.txt.sig are in the current directory) with:

gpg --verify manifest-v4.0.6-pre1.txt.sig manifest-v4.0.6-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.0.6-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.

Amber 4.0.5

Implemented pagination in the application, logs and activities screen
Fix database size calculation inside the settings screen
Optimize getSavedRelays to query unique relay lists directly
Remove application name pre-loading in IncomingRequestScreen
Use direct DELETE queries for clearing old logs and history instead of iterative deletion

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

gpg --verify manifest-v4.0.5.txt.sig manifest-v4.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 <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.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.

Amber 4.0.4

Fix NullPointerException
Improve activity screen performance
Add some event kinds translations

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

gpg --verify manifest-v4.0.4.txt.sig manifest-v4.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 <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.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.

Amber 4.0.3

Fix close application logic for bunkers
Add a Export/Import accounts method by @npub1acr7ycax3t7ne8xzt0kfhh33cfd5z4h8z3ntk00erpd7zxlqzy3qrn2tqw
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 @npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5
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, 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.0.3.txt and manifest-v4.0.3.txt.sig are in the current directory) with:

gpg --verify manifest-v4.0.3.txt.sig manifest-v4.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 <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.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.

Amber 4.0.3-pre2

Fix close application logic for bunkers
Add a Export/Import accounts method by @npub1acr7ycax3t7ne8xzt0kfhh33cfd5z4h8z3ntk00erpd7zxlqzy3qrn2tqw
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 @npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5
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, 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.0.3-pre2.txt and manifest-v4.0.3-pre2.txt.sig are in the current directory) with:

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:

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.0.3-pre2.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.

Amber 4.0.3-pre1

Fix close application logic for bunkers
Add a Export/Import accounts method by @npub1acr7ycax3t7ne8xzt0kfhh33cfd5z4h8z3ntk00erpd7zxlqzy3qrn2tqw
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 @npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5
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, 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.0.3-pre1.txt and manifest-v4.0.3-pre1.txt.sig are in the current directory) with:

gpg --verify manifest-v4.0.3-pre1.txt.sig manifest-v4.0.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.0.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.

Amber 4.0.2

Change Dockerfile to build from the local repo
Show all accounts in the backup screen
Show the backup dialog if any account needs backup
Enable gradle configuration cache
Fix migration from old version
Fix 404 link in README by @npub1lczxedq435kkzvuhf04kpxh67alqs4sa4glv24xfy6nw5tvwnwxqhwwxyr

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

gpg --verify manifest-v4.0.2.txt.sig manifest-v4.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 <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.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.

Amber 4.0.2-pre1

Change Dockerfile to build from the local repo
Show all accounts in the backup screen
Show the backup dialog if any account needs backup
Enable gradle configuration cache
Fix migration from old version

Download it with zapstore.dev, 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.0.2-pre1.txt and manifest-v4.0.2-pre1.txt.sig are in the current directory) with:

gpg --verify manifest-v4.0.2-pre1.txt.sig manifest-v4.0.2-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.0.2-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.

Releases: greenart7c3/Amber

Release v4.0.6

Amber 4.0.6

Verifying the release

Uh oh!

Release v4.0.6-pre2

Amber 4.0.6-pre2

Verifying the release

Uh oh!

Release v4.0.6-pre1

Amber 4.0.6-pre1

Verifying the release

Uh oh!

Release v4.0.5

Amber 4.0.5

Verifying the release

Uh oh!

Release v4.0.4

Amber 4.0.4

Verifying the release

Uh oh!

Release v4.0.3

Amber 4.0.3

Verifying the release

Uh oh!

Release v4.0.3-pre2

Amber 4.0.3-pre2

Verifying the release

Uh oh!

Release v4.0.3-pre1

Amber 4.0.3-pre1

Verifying the release

Uh oh!

Release v4.0.2

Amber 4.0.2

Verifying the release

Uh oh!

Release v4.0.2-pre1

Amber 4.0.2-pre1

Verifying the release

Uh oh!