## 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](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.0.6)
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.0.6.txt` and `manifest-v4.0.6.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.6.txt.sig manifest-v4.0.6.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.0.6.txt
```
One can use the `shasum -a 256
I think you can, never tried it to see if it breaks anything after a while
## 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](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.0.5)
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.0.5.txt` and `manifest-v4.0.5.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.5.txt.sig manifest-v4.0.5.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.0.5.txt
```
One can use the `shasum -a 256
I improved the performance and will release a new version on monday
Never seen this one before. I'll try to find out what is happening, maybe its some relay misconfiguration
## Amber 4.0.4
- Fix NullPointerException
- Improve activity screen performance
- Add some event kinds translations
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.0.4)
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.0.4.txt` and `manifest-v4.0.4.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.4.txt.sig manifest-v4.0.4.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.0.4.txt
```
One can use the `shasum -a 256
## Amber 4.0.3
- Fix close application logic for bunkers
- Add a Export/Import accounts method by nostr:nprofile1qqswuplzvwng4lfunnp9hmymmccuyk6p2mn3ge4m8hu3sklpr0spzgsppemhxue69uhkummn9ekx7mp0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsanh2yp
- 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 nostr:nprofile1qqspw5udc2nzw6wsj3plrrphe0343744h0ucz9e4g248chl3w8kh03qpzpmhxue69uhkumewwd68ytnrwghszrnhwden5te0dehhxtnvdakz7qg6waehxw309ac8junpd45kgtnxd9shg6npvchxxmmd9uygkqly
- 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](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.0.3)
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.0.3.txt` and `manifest-v4.0.3.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.3.txt.sig manifest-v4.0.3.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.0.3.txt
```
One can use the `shasum -a 256
## Amber 4.0.3-pre2
- Fix close application logic for bunkers
- Add a Export/Import accounts method by nostr:nprofile1qqswuplzvwng4lfunnp9hmymmccuyk6p2mn3ge4m8hu3sklpr0spzgsppemhxue69uhkummn9ekx7mp0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsanh2yp
- 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 nostr:nprofile1qqspw5udc2nzw6wsj3plrrphe0343744h0ucz9e4g248chl3w8kh03qpzpmhxue69uhkumewwd68ytnrwghszrnhwden5te0dehhxtnvdakz7qg6waehxw309ac8junpd45kgtnxd9shg6npvchxxmmd9uygkqly
- 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](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.0.3-pre2)
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.0.3-pre2.txt` and `manifest-v4.0.3-pre2.txt.sig` are in the current directory) with:
``` bash
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:
``` 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.0.3-pre2.txt
```
One can use the `shasum -a 256
## 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](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.0.2)
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.0.2.txt` and `manifest-v4.0.2.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.2.txt.sig manifest-v4.0.2.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.0.2.txt
```
One can use the `shasum -a 256
## Amber 4.0.1
- Fix reproducibility and added instruction in the README
- Fix the validation of the current logged in user when sending a event from another user
- When using intents send a reject response
- Fix the edit permissions screen not updating correctly the fields when rejecting/accepting a permission
- Update to gradle 9
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.0.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.0.1.txt` and `manifest-v4.0.1.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.1.txt.sig manifest-v4.0.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.0.1.txt
```
One can use the `shasum -a 256
Your link to zapstore links to old url which is now used by some shitcoin project. The correct url is https://zapstore.dev/
Thanks
## Amber 4.0.0
- Refactor everything to use the new quartz update
- Fix reconnection issues
- Kill switch feature
Download it with [zap.store](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.0.0)
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.0.0.txt` and `manifest-v4.0.0.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.0.txt.sig manifest-v4.0.0.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.0.0.txt
```
One can use the `shasum -a 256
## Amber 4.0.0-pre2
- Refactor everything to use the new quartz update
- Fix reconnection issues
- Kill switch feature
Download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.0-pre2)
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.0.0-pre2.txt` and `manifest-v4.0.0-pre2.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.0-pre2.txt.sig manifest-v4.0.0-pre2.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.0.0-pre2.txt
```
One can use the `shasum -a 256
## Amber 4.0.0-pre1
- Refactor everything to use the new quartz update
Download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.0-pre1)
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.0.0-pre1.txt` and `manifest-v4.0.0-pre1.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.0-pre1.txt.sig manifest-v4.0.0-pre1.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.0.0-pre1.txt
```
One can use the `shasum -a 256
## Amber 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](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/v3.4.5)
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-v3.4.5.txt` and `manifest-v3.4.5.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v3.4.5.txt.sig manifest-v3.4.5.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-v3.4.5.txt
```
One can use the `shasum -a 256
## Amber 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](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/v3.4.2)
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-v3.4.2.txt` and `manifest-v3.4.2.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v3.4.2.txt.sig manifest-v3.4.2.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-v3.4.2.txt
```
One can use the `shasum -a 256
## Amber 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](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/v3.4.2-pre2)
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-v3.4.2-pre2.txt` and `manifest-v3.4.2-pre2.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v3.4.2-pre2.txt.sig manifest-v3.4.2-pre2.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-v3.4.2-pre2.txt
```
One can use the `shasum -a 256