Citrine / Citrine is on Nostr

Last Notes

2026-03-11 14:25:57 UTC

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

2026-02-09 14:22:12 UTC

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

2026-01-16 12:16:12 UTC

- reply

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

2026-01-16 12:14:22 UTC

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

2026-01-10 11:59:27 UTC

- reply

To host static WebApps like jumble or coracle

2026-01-10 11:57:28 UTC

- reply

You are probably using the wrong port the default is 4869

2026-01-06 10:16:50 UTC

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

2025-11-17 18:19:58 UTC

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

2025-05-30 16:05:27 UTC

- reply

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

2024-12-31 11:14:25 UTC

- reply

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

2024-11-30 13:28:31 UTC

- reply

Yes

2024-10-25 14:19:56 UTC

- reply

Fixed in 0.5.4