Releases: greenart7c3/Amber
Release v4.0.0-pre1
d3fcfb8Amber 4.0.0-pre1
- Refactor everything to use the new quartz update
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 44F0AAEB77F373747E3D5444885822EED3A26A6DOnce you have his PGP key you can verify the release (assuming manifest-v4.0.0-pre1.txt and manifest-v4.0.0-pre1.txt.sig are in the current directory) with:
gpg --verify manifest-v4.0.0-pre1.txt.sig manifest-v4.0.0-pre1.txtYou 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.0-pre1.txtOne 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 v3.4.6
a37611bAmber 3.4.6
- Fixed kind not being saved when rejecting an event from a native app forever
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 44F0AAEB77F373747E3D5444885822EED3A26A6DOnce you have his PGP key you can verify the release (assuming manifest-v3.4.6.txt and manifest-v3.4.6.txt.sig are in the current directory) with:
gpg --verify manifest-v3.4.6.txt.sig manifest-v3.4.6.txtYou 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-v3.4.6.txtOne 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 v3.4.5
0feced9Amber 3.4.5
- Added a button in notifications and AppBar to restart connection to relays
- When connecting to relay try sending the subscription again
- If there’s a error sending a message to the relay try restarting it and sending again
- Check for encryption type again (not every app has support for nip44 yet)
- Revert QrCode reader support for multi-window (it was not reading inverted QrCodes)
- Generate a new event when there’s an error instead of trying to send the same event to avoid receiving duplicated messages from relays
- Send a error notification if it was not possible to send the event to the relays
- Close the app first and then try to send the event to the 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
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 44F0AAEB77F373747E3D5444885822EED3A26A6DOnce you have his PGP key you can verify the release (assuming manifest-v3.4.5.txt and manifest-v3.4.5.txt.sig are in the current directory) with:
gpg --verify manifest-v3.4.5.txt.sig manifest-v3.4.5.txtYou 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-v3.4.5.txtOne 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 v3.4.5-pre1
Amber 3.4.5-pre1
- Added a button in notifications and AppBar to restart connection to relays
- When connecting to relay try sending the subscription again
- If there’s a error sending a message to the relay try restarting it and sending again
- Check for encryption type again (not every app has support for nip44 yet)
- Revert QrCode reader support for multi-window (it was not reading inverted QrCodes)
- Generate a new event when there’s an error instead of trying to send the same event to avoid receiving duplicated messages from relays
- Send a error notification if it was not possible to send the event to the relays
- Close the app first and then try to send the event to the 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
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 44F0AAEB77F373747E3D5444885822EED3A26A6DOnce you have his PGP key you can verify the release (assuming manifest-v3.4.5-pre1.txt and manifest-v3.4.5-pre1.txt.sig are in the current directory) with:
gpg --verify manifest-v3.4.5-pre1.txt.sig manifest-v3.4.5-pre1.txtYou 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-v3.4.5-pre1.txtOne 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 v3.4.4
e2010fbAmber 3.4.4
- Fix get_public_key not working for some native apps
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 44F0AAEB77F373747E3D5444885822EED3A26A6DOnce you have his PGP key you can verify the release (assuming manifest-v3.4.4.txt and manifest-v3.4.4.txt.sig are in the current directory) with:
gpg --verify manifest-v3.4.4.txt.sig manifest-v3.4.4.txtYou 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-v3.4.4.txtOne 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 v3.4.3
2799e12Amber 3.4.3
- Fix crash when sending multiple intents
- Move profile fetch to its own file
- Change the clear logs task to a workManager
- Start the clear logs only after 5 minutes
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 44F0AAEB77F373747E3D5444885822EED3A26A6DOnce you have his PGP key you can verify the release (assuming manifest-v3.4.3.txt and manifest-v3.4.3.txt.sig are in the current directory) with:
gpg --verify manifest-v3.4.3.txt.sig manifest-v3.4.3.txtYou 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-v3.4.3.txtOne 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 v3.4.2
c67fc02Amber 3.4.2
- Added loading indicator when running migrations
- Fix ncryptsec export
- Add a icon when using a proxy and check if the proxy is working
- Add more event translations
- Add a screen to send feedback on nostr
- Start separating Bunker and native implementations
- Fix service start error in slow devices when the user moves the app to the background faster than the app can start
- Fix scrollbar position
- Fix requests not disappearing when accepting/rejecting
- Fix QR code scanner when using multiwindow mode
- Use datasource to fetch profile data
- Remove check for paid and auth in relays
- Remove listening for new connections option
- Make secret mandatory for bunker requests
- Update notification less often
- Updated dependencies
- Separated Bunker and Intent logic
- Fixed bunker relay validation when adding a new relay
- Option to reuse an existing connection
- New activities screen
- Always encrypt bunker responses with nip 44
- Target android 16
- Add some error handling to check for network permissions
- Remove gson dependency
- Add more 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
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 44F0AAEB77F373747E3D5444885822EED3A26A6DOnce you have his PGP key you can verify the release (assuming manifest-v3.4.2.txt and manifest-v3.4.2.txt.sig are in the current directory) with:
gpg --verify manifest-v3.4.2.txt.sig manifest-v3.4.2.txtYou 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-v3.4.2.txtOne 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 v3.4.2-pre4
202ca88Amber 3.4.2-pre4
- Added loading indicator when running migrations
- Fix ncryptsec export
- Add a icon when using a proxy and check if the proxy is working
- Add more event translations
- Add a screen to send feedback on nostr
- Start separating Bunker and native implementations
- Fix service start error in slow devices when the user moves the app to the background faster than the app can start
- Fix scrollbar position
- Fix requests not disappearing when accepting/rejecting
- Fix QR code scanner when using multiwindow mode
- Use datasource to fetch profile data
- Remove check for paid and auth in relays
- Remove listening for new connections option
- Make secret mandatory for bunker requests
- Update notification less often
- Updated dependencies
- Separated Bunker and Intent logic
- Fixed bunker relay validation when adding a new relay
- Option to reuse an existing connection
- New activities screen
- Always encrypt bunker responses with nip 44
- Target android 16
- Add some error handling to check for network permissions
- Remove gson dependency
- Fix Bunker events not working in 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 44F0AAEB77F373747E3D5444885822EED3A26A6DOnce you have his PGP key you can verify the release (assuming manifest-v3.4.2-pre4.txt and manifest-v3.4.2-pre4.txt.sig are in the current directory) with:
gpg --verify manifest-v3.4.2-pre4.txt.sig manifest-v3.4.2-pre4.txtYou 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-v3.4.2-pre4.txtOne 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 v3.4.2-pre3
dd2908dAmber 3.4.2-pre3
- Added loading indicator when running migrations
- Fix ncryptsec export
- Add a icon when using a proxy and check if the proxy is working
- Add more event translations
- Add a screen to send feedback on nostr
- Start separating Bunker and native implementations
- Fix service start error in slow devices when the user moves the app to the background faster than the app can start
- Fix scrollbar position
- Fix requests not disappearing when accepting/rejecting
- Fix QR code scanner when using multiwindow mode
- Use datasource to fetch profile data
- Remove check for paid and auth in relays
- Remove listening for new connections option
- Make secret mandatory for bunker requests
- Update notification less often
- Updated dependencies
- Separated Bunker and Intent logic
- Fixed bunker relay validation when adding a new relay
- Option to reuse an existing connection
- New activities screen
- Always encrypt bunker responses with nip 44
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 44F0AAEB77F373747E3D5444885822EED3A26A6DOnce you have his PGP key you can verify the release (assuming manifest-v3.4.2-pre3.txt and manifest-v3.4.2-pre3.txt.sig are in the current directory) with:
gpg --verify manifest-v3.4.2-pre3.txt.sig manifest-v3.4.2-pre3.txtYou 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-v3.4.2-pre3.txtOne 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 v3.4.2-pre2
41724adAmber 3.4.2-pre2
- Added loading indicator when running migrations
- Fix ncryptsec export
- Add a icon when using a proxy and check if the proxy is working
- Add more event translations
- Add a screen to send feedback on nostr
- Start separating Bunker and native implementations
- Fix service start error in slow devices when the user moves the app to the background faster than the app can start
- Fix scrollbar position
- Fix requests not disappearing when accepting/rejecting
- Fix QR code scanner when using multiwindow mode
- Use datasource to fetch profile data
- Remove check for paid and auth in relays
- Remove listening for new connections option
- Make secret mandatory for bunker requests
- Update notification less often
- Updated dependencies
- Separated Bunker and Intent logic
- Fixed bunker relay validation when adding a new relay
- Option to reuse an existing connection
- New activities 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 44F0AAEB77F373747E3D5444885822EED3A26A6DOnce you have his PGP key you can verify the release (assuming manifest-v3.4.2-pre2.txt and manifest-v3.4.2-pre2.txt.sig are in the current directory) with:
gpg --verify manifest-v3.4.2-pre2.txt.sig manifest-v3.4.2-pre2.txtYou 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-v3.4.2-pre2.txtOne 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.