mirror of
https://github.com/greenart7c3/Amber.git
synced 2026-10-05 19:08:23 +00:00
Claude
d48491cf7a
Add one file per GitHub release from 0.0.1 through 6.1.0-pre3, including pre-releases (185 files), with release bodies kept verbatim. Releases published without notes get a placeholder line. Regenerate the README index to list all 190 versions newest first. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JnvVcrZbefZviFqfG8bgPU
60 lines
2.9 KiB
Markdown
60 lines
2.9 KiB
Markdown
# Amber 3.2.8
|
||
|
||
- refactor NostrSigner.getInstance() into NostrSigner.instance
|
||
- refactor: removed appDatase from parameters
|
||
- fix logged account switch when using bunkers
|
||
- Use bunker response from quartz
|
||
- Remove bunker request from the content pending intent
|
||
- Open amber when pressing the connected relays notification
|
||
- Fix connected relays notification
|
||
- Include zapstore in the new bunker and initial message
|
||
- Only show a backup message after sign up
|
||
- Add search to the activity screen
|
||
- Delete old logs and activities automatically
|
||
- Show option to never close the app when using bunker url
|
||
- Fix application activity logs not saving correctly
|
||
- Move relay listeners to it’s own files
|
||
- Cast to lowercase and trim data when logging in
|
||
- Separate general prefs and account prefs keys
|
||
- Fix tor connection when using a local relay
|
||
- Add loading indicator when trying to fetch profile picture
|
||
- Use Hex.decode from quartz instead of acinq
|
||
- Retry sending events when it fails
|
||
- Better message when orbot/tor is not working
|
||
- Only show orbot/tor in the login/signup once
|
||
- Fix connection check when sending an event
|
||
|
||
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.2.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-v3.2.6.txt` and `manifest-v3.2.6.txt.sig` are in the current directory) with:
|
||
|
||
``` bash
|
||
gpg --verify manifest-v3.2.6.txt.sig manifest-v3.2.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 <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:
|
||
|
||
``` bash
|
||
cat manifest-v3.2.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.
|