LibreNostr v0.2.4

Two accounts on the same device already shared their relay connections and local cache; the cleanup and search-feed code paths had not caught up with that.

Fixed

• Logging out one account discarded shared cache other logged-in accounts were still using. The coordinator's follow-list cache and hot event layer are one process-wide instance, shared by every account signed in on the device — logging out account A used to wipe both unconditionally, even with account B still logged in and relying on them. It is now reset only when the account being removed was the last one signed in.
• Advanced search's myfollows scope asked relays directly instead of going through the fetch coordinator. This was the case named when the coordinator was introduced — the note feed, article feed and advanced search all want the same follow list, often within the same burst of tab loads — but this call site was never actually wired to it. It now shares the same coalesced, briefly-cached request as everything else.

Verifying this release

Every APK is signed with the same key across releases (CN=Lwb89dev, O=LibreNostr). Verify with:

apksigner verify --print-certs librenostr-0.2.4-<abi>.apk
sha256sum -c SHA256SUMS.txt

Pick the APK matching your device's CPU architecture (arm64-v8a covers virtually all phones from the last several years).