greenart7c3/Citrine v3.2.4

Release v3.2.4

on GitHub

Citrine 3.2.4

• Citrine no longer stores the contact lists of people you don't follow: they are fetched only for your own follow graph, and the ones already stored for strangers are deleted once (this freed about 900 MB on a 1.26 GB database)
• Exporting a backup no longer loads every event id and a thousand events at once, so a large database can be exported without running out of memory
• A request that runs out of memory now fails on its own with "relay out of memory" instead of taking the whole relay down
• Crash reports are now written before the app is killed (out-of-memory reports are no longer dropped) and include the failing thread, Java/native heap and database sizes
• On Android 11+, the crash dialog now also reports deaths that are not Java crashes, such as ANRs, low-memory kills and native crashes
• The relay answers much faster now: unfiltered queries went from about 2 s to 0.15 s, and "#e" tag queries from 436 ms to 188 ms

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

gpg --verify manifest-v3.2.4.txt.sig manifest-v3.2.4.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.2.4.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.