SecureChat365 v0.1.4

Fix Tauri event channel name: backend emitted 'veil', frontend listened for 'securechat365'

SecureChat365 v0.1.3

Fix RELAY_URL in CI; restore connection indicator and mobile safe areas

SecureChat365 v0.1.2

Contact verification now works.

Key bundles carry an Ed25519 signature over the identity key, so the two keys are cryptographically bound and safety numbers compare the right person. Previously the verification screen showed digits that could never match.

All devices must update together. v0.1.0 and v0.1.2 clients cannot exchange key bundles. Reset your identity and re-add contacts after updating.

Still alpha, still unsigned, still not audited. Verify against SHA256SUMS.txt or build from source.

SecureChat365 v0.1.1

Contact verification now works.

Key bundles carry an Ed25519 signature over the identity key, so the two keys are cryptographically bound and safety numbers compare the right person. Previously the verification screen showed digits that could never match.

All devices must update together. v0.1.0 and v0.1.1 clients cannot exchange key bundles. Reset your identity and re-add contacts after updating.

Still alpha, still unsigned, still not audited. Verify against SHA256SUMS.txt or build from source.

SecureChat365 v0.1.0

First public build.

Alpha, and not audited. Contact verification is incomplete — see the README for the full list of known gaps.

These builds are unsigned. macOS reports unsigned apps as damaged, which is misleading: right-click the app and choose Open. Windows shows a SmartScreen warning. Both warnings are accurate in that nothing has vouched for these files — verify against SHA256SUMS.txt, or build from source.