Nostr notes by Citrine

## Citrine 2.0.0 - Improve the relay performance by changing the ...

2026-03-11T14:25:57Z

## Citrine 2.0.0

- Improve the relay performance by changing the indexes, database queries and how the kotlin coroutines run
- Better performance when hosting web apps
- Start each web app in their own port
- Better interface for the events screen
- Updated dependencies
- Use FTS for search queries
- Support for expanding the event in the event screen
- Option for downloading tagged events

Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqtkxmmd9enhyet9deshyaphvvejucmfw3exjmn9hzj8uf), [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/v2.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-v2.0.0.txt` and `manifest-v2.0.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v2.0.0.txt.sig manifest-v2.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 <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-v2.0.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 2.0.0-pre1 - Improve the relay performance by changing ...

2026-02-09T14:22:12Z

## Citrine 2.0.0-pre1

- Improve the relay performance by changing the indexes, database queries and how the kotlin coroutines run
- Better performance when hosting web apps
- Start each web app in their own port
- Better interface for the events screen
- Updated dependencies

Download it with [zapstore.dev](https://zapstore.dev/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/v2.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-v2.0.0-pre1.txt` and `manifest-v2.0.0-pre1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v2.0.0-pre1.txt.sig manifest-v2.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 <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-v2.0.0-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.

The correct version is signed by @nprofile…xcpk not franzap

2026-01-16T12:16:12Z

In reply to nevent1q…f5yx
_________________________

The correct version is signed by greenart7c3 (nprofile…xcpk) not franzap

## Citrine 1.0.1 - Performance improvements in content resolver ...

2026-01-16T12:14:22Z

## Citrine 1.0.1

- Performance improvements in content resolver by ₿ (nprofile…48vj)
- Fix SQL injection by ₿ (nprofile…48vj)
- Proper error handling in content resolver by ₿ (nprofile…48vj)

Download it with [zapstore.dev](https://zapstore.dev/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/v1.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-v1.0.1.txt` and `manifest-v1.0.1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v1.0.1.txt.sig manifest-v1.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 <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-v1.0.1.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.

To host static WebApps like jumble or coracle

2026-01-10T11:59:27Z

In reply to nevent1q…l97x
_________________________

To host static WebApps like jumble or coracle

You are probably using the wrong port the default is 4869

2026-01-10T11:57:28Z

In reply to nevent1q…naz7
_________________________

You are probably using the wrong port the default is 4869

## Citrine 1.0.0 - Added crash report handler - Support for ...

2026-01-06T10:16:50Z

## Citrine 1.0.0

- Added crash report handler
- Support for content resolver by ₿ (nprofile…549x)
- Broadcast events to relays when back online by ₿ (nprofile…549x)
- Added some missing string resources from settings screen
- Host web apps
- Better performance when loading the kind field

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/v1.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-v1.0.0.txt` and `manifest-v1.0.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v1.0.0.txt.sig manifest-v1.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 <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-v1.0.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.9.0 - Migrate to new quartz version - Add proxy to ...

2025-11-17T18:19:58Z

## 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 <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-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 ...

2025-08-18T18:36:25Z

## 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 fiatjaf (nprofile…xuyp)
- Make protected events readable by anyone by fiatjaf (nprofile…xuyp)
- Fix EOSE message by fiatjaf (nprofile…xuyp)
- Allow localhost access to bypass nip 70 checks by fiatjaf (nprofile…xuyp)
- Dispatch events to subscriptions from the same connection it came from by fiatjaf (nprofile…xuyp)

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

2025-05-30T16:05:27Z

In reply to nevent1q…nywp
_________________________

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

2024-12-31T11:14:25Z

In reply to nevent1q…0ayp
_________________________

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

Yes

2024-11-30T13:28:31Z

In reply to nevent1q…a8hx
_________________________

Yes

Fixed in 0.5.4

2024-10-25T14:19:56Z

In reply to nevent1q…3jlp
_________________________

Fixed in 0.5.4