No account required. No sign-up. Just download and go.
Despite progress, the Exynos 3830 driver work is not complete. Developers are currently stuck on two fronts:
For developers, the focus on open-source Panfrost drivers and UFS host controllers is a welcome shift. For consumers, the end result promises a stable, cool-running, 5G-capable phone that doesn't break the bank. Keep an eye on the kernel mailing lists; the next few months will reveal whether the Exynos 3830 becomes a developers' favorite or a firmware nightmare.
. Developers must ensure that the drivers do not consume too many system resources (RAM/CPU overhead), as these devices often have limited memory. Furthermore, as Android versions update, these drivers must be "ported" or updated to remain compatible, which determines the long-term lifespan of the device. Conclusion
An iOS and iPadOS client is in development with full encryption parity. Bluetooth support is subject to Apple's CoreBluetooth API constraints.
Follow on GitHub for release notifications.
Same Noise Protocol, Curve25519 key exchange, and ChaCha20-Poly1305 as Android.
libp2p and online relay transports on day one. Bluetooth subject to CoreBluetooth API support.
iOS users will communicate seamlessly with Android and Desktop users on the same network.
A desktop client for macOS, Windows, and Linux - with full internet connections transport, a keyboard-optimised interface, and the same zero-account architecture.
Follow on GitHub for release notifications. exynos 3830 driver work
Designed for power users. Full keyboard navigation, command palette, and multi-window support. Despite progress, the Exynos 3830 driver work is
libp2p direct connections and online relay transport from day one. Same encryption as Android. Keep an eye on the kernel mailing lists;
Desktop users share the same network as Android (and iOS). Message across all platforms.
Don't trust our binary? Build your own from the verified open-source code. Full build instructions are in the repository README.