Citrine's avatar
Citrine 2 weeks ago
## 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](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/v3.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-v3.0.0-pre1.txt` and `manifest-v3.0.0-pre1.txt.sig` are in the current directory) with: ``` bash 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: ``` 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.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.

Replies (7)

Its a modern implementation in rust, and apparently way better than the ctor client across the board. I think kmp-tor wraps around that ctor client. Unfortunately arti doesnt have kotlin bindings yet...
Works great, even over Tor. If I expose the relay over Tor, where do I find the address? One request, could there be an option to not delete kind 0 based on age (maybe relay lists too)? They are sometimes not updated often, and it would be nice to have them locally. Also I'm not sure if this is a bug, or working as intended. The "accept events signed by" option removes notes found by the aggregator. I can see why it is this way, but it makes the aggregation less useful.
Citrine's avatar
Citrine 2 weeks ago
You can find the address at the home screen I forgot about the accept events signed by option, will fix it next version I'll also add a option to not delete some kinds