Release v3.0.0

Citrine 3.0.0

• Added Negentropy (NIP-77) support
• Added external signer and NIP-42 AUTH support to the relay aggregator
• Honor NIP-51 mute lists in the relay aggregator
• Cap the relay aggregator at 3 relays per author with configurable source and indexer relays
• Reuse cached follow/mute/metadata on aggregator restart and network change
• Pause the relay aggregator on limited/restricted networks
• Filter onion relay URLs from the aggregator when the outbound proxy is disabled
• Reject reposts that embed protected events
• Show local, Wi-Fi, and Tor addresses with copy actions on the home screen
• Redesigned settings screen split into a hub with category sub-screens
• Preserve mute lists from age-based deletion by default
• Added option to preserve specific event kinds from age-based deletion
• Made the ephemeral mute response a setting, defaulting to off
• Reduced relay aggregator battery drain
• Performance improvements on the relay hot path and event-receive path
• Fixed WebSocket connections that sometimes don't close
• Skip duplicate foreground service notifications
• Dedupe AUTH challenges so external signers are not re-prompted
• Updated Gradle and refreshed library dependencies
• Updated translations

Download it with Zapstore, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

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:

gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D

Once you have his PGP key you can verify the release (assuming manifest-v3.0.0.txt and manifest-v3.0.0.txt.sig are in the current directory) with:

gpg --verify manifest-v3.0.0.txt.sig manifest-v3.0.0.txt

You should see the following if the verification was successful:

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:

cat manifest-v3.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.

Release v3.0.0-pre2

Citrine 3.0.0-pre2

• Added Negentropy (NIP-77) support
• Added external signer and NIP-42 AUTH support to the relay aggregator
• Honor NIP-51 mute lists in the relay aggregator
• Cap the relay aggregator at 3 relays per author with configurable source and indexer relays
• Reject reposts that embed protected events
• Show local, Wi-Fi, and Tor addresses with copy actions on the home screen
• Redesigned settings screen split into a hub with category sub-screens
• Preserve mute lists from age-based deletion by default
• Added option to preserve specific event kinds from age-based deletion
• Reduced relay aggregator battery drain
• Performance improvements on the relay hot path and event-receive path
• Skip duplicate foreground service notifications
• Dedupe AUTH challenges so external signers are not re-prompted
• Updated translations

Download it with Zapstore, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

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:

gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D

Once you have his PGP key you can verify the release (assuming manifest-v3.0.0-pre2.txt and manifest-v3.0.0-pre2.txt.sig are in the current directory) with:

gpg --verify manifest-v3.0.0-pre2.txt.sig manifest-v3.0.0-pre2.txt

You should see the following if the verification was successful:

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:

cat manifest-v3.0.0-pre2.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.

Release v3.0.0-pre1

Citrine 3.0.0-pre1

• Improved websocket performance
• Support for built in tor
• Support for acting as a relay aggregator
• Improve performance when downloading your events
• Added a pie chart in the events screen

Download it with Zapstore, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

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:

gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D

Once you have his PGP key you can verify the release (assuming manifest-v3.0.0-pre1.txt and manifest-v3.0.0-pre1.txt.sig are in the current directory) with:

gpg --verify manifest-v3.0.0-pre1.txt.sig manifest-v3.0.0-pre1.txt

You should see the following if the verification was successful:

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:

cat manifest-v3.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.

Release v2.0.0

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, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

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:

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:

gpg --verify manifest-v2.0.0.txt.sig manifest-v2.0.0.txt

You should see the following if the verification was successful:

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:

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.

Release v2.0.0-pre2

Citrine 2.0.0-pre2

• 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

Download it with Zapstore, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

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:

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

gpg --verify manifest-v2.0.0-pre2.txt.sig manifest-v2.0.0-pre2.txt

You should see the following if the verification was successful:

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:

cat manifest-v2.0.0-pre2.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.

Release v2.0.0-pre1

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, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

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:

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:

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:

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:

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.

Release v1.0.2

Citrine 1.0.2

• Fix a crash when trying to restore follows

Download it with zap.store, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

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:

gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D

Once you have his PGP key you can verify the release (assuming manifest-v1.0.2.txt and manifest-v1.0.2.txt.sig are in the current directory) with:

gpg --verify manifest-v1.0.2.txt.sig manifest-v1.0.2.txt

You should see the following if the verification was successful:

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:

cat manifest-v1.0.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.

Release v1.0.1

Citrine 1.0.1

• Performance improvements in content resolver by @npub1kpv7arjpaa3f37x9m9cu6sk9weeykt84kcrkd070m4amcmuk0r8sk74mkw
• Fix SQL injection by @npub1kpv7arjpaa3f37x9m9cu6sk9weeykt84kcrkd070m4amcmuk0r8sk74mkw
• Proper error handling in content resolver by @npub1kpv7arjpaa3f37x9m9cu6sk9weeykt84kcrkd070m4amcmuk0r8sk74mkw

Download it with zap.store, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

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:

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:

gpg --verify manifest-v1.0.1.txt.sig manifest-v1.0.1.txt

You should see the following if the verification was successful:

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:

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.

Release v1.0.0

Citrine 1.0.0

• Added crash report handler
• Support for content resolver by @npub1kpv7arjpaa3f37x9m9cu6sk9weeykt84kcrkd070m4amcmuk0r8sk74mkw
• Broadcast events to relays when back online by @npub1kpv7arjpaa3f37x9m9cu6sk9weeykt84kcrkd070m4amcmuk0r8sk74mkw
• Added some missing string resources from settings screen
• Host web apps
• Better performance when loading the kind field

Download it with zap.store, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

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:

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:

gpg --verify manifest-v1.0.0.txt.sig manifest-v1.0.0.txt

You should see the following if the verification was successful:

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:

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.

Release v0.9.0

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, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

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:

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:

gpg --verify manifest-v0.9.0.txt.sig manifest-v0.9.0.txt

You should see the following if the verification was successful:

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:

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.