Citrine 3.2.5
- The relay now refuses more than 50 WebSocket connections and caps the incoming frame size, the per-connection queues and the outbound buffers, so memory no longer grows with the number of clients and one slow client can no longer hold hundreds of megabytes: this fixes the out-of-memory crashes large relays were dying from
- Removing the contact lists of people you don't follow now runs in small pages, so it no longer loads every contact list into memory at once and it resumes where it stopped if it is interrupted
- Crash reports are now sent from Citrine itself: the report opens in an editable full screen with "Sign with Amber" (so the developer can reply to you) or "Send anonymously", instead of being copied to the clipboard for you to paste somewhere
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 44F0AAEB77F373747E3D5444885822EED3A26A6DOnce you have his PGP key you can verify the release (assuming manifest-v3.2.5.txt and manifest-v3.2.5.txt.sig are in the current directory) with:
gpg --verify manifest-v3.2.5.txt.sig manifest-v3.2.5.txtYou 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.2.5.txtOne 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.
Previous release notes live in docs/changelogs.