## Citrine 0.9.0

- Migrate to new quartz version
- Add proxy to the settings screen
- Add backup setup in the settings screen
- Keep the last 5 backups
- Update dependencies
- Fix import and export missing some events

Download it with [zap.store](https://zap.store/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.citrine) or download it directly in the [releases page
](https://github.com/greenart7c3/Citrine/releases/tag/v0.9.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-v0.9.0.txt` and `manifest-v0.9.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v0.9.0.txt.sig manifest-v0.9.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 <[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:

``` bash
cat manifest-v0.9.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.

## Citrine 0.8.2

- Close connections when it’s sending invalid frames
- Better handling of disconnections
- refactors how WebSocket connections and subscriptions are managed
- Support for mute
- Always accepts ephemeral events
- Fix auth command results by @nprofile1q...
- Make protected events readable by anyone by @nprofile1q...
- Fix EOSE message by @nprofile1q...
- Allow localhost access to bypass nip 70 checks by @nprofile1q...
- Dispatch events to subscriptions from the same connection it came from by @nprofile1q...

Download it with [zap.store](https://zap.store/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.citrine) or download it directly in the [releases page
](https://github.com/greenart7c3/Citrine/releases/tag/v0.8.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-v0.8.2.txt` and `manifest-v0.8.2.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v0.8.2.txt.sig manifest-v0.8.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 <[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:

``` bash
cat manifest-v0.8.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.

I don't remember who made a guide now, you can just put ws://127.0.0.1:4869 in the local relays and private home relays sections in amethyst

I'll see if I can add support for it in January

Yes

Fixed in 0.5.4