wire-android VS session-desktop

Wire: Gplay || F-droid || GitHub

Note that it doesn't mean you need to write your whole library in Scala 2.11. You can write it in 2.13, but then your build script must have an option to compile it with 2.11. You can see for example how it is done in wire-signals, an event stream library I worked on (https://github.com/wireapp/wire-signals/blob/main/core/build.sbt). wire-signals was then used in Wire Android, an Android client for the end-to-end encrypted messenger, Wire. You can search for "wireSignals" in this Gradle script: https://github.com/wireapp/wire-android/blob/develop/app/build.gradle (Wire Android is probably the biggest Android app ever written in Scala).

Scala and a bit of Rust: https://github.com/wireapp/wire-android

The current (still maintained) Android client of Wire, an end-to-end encrypted messenger, is written in Scala 2.11: https://github.com/wireapp/wire-android However, the new version is in progress and it will be in Kotlin.

Hey, same problem! I even opened a bug report at the time, which devs said they couldn't replicate :(.

I just looked last week out of curiosity. Apparently they figured it out sometime in 2019, and it had something to do with avatars. How odd.

Specifically, check the reply from LNFelton here - https://github.com/wireapp/wire-android/issues/777

The Client is GPL-3.0 Licensed. (WebApp,Desktop,iOS,Android) The Server is AGPL-3.0 Licensed. Both Client and Server are Open-Source.

Wire • Secure Messenger: Wire offers highly secure communication – anywhere and anytime.

Source: https://github.com/wireapp/wire-android

Wire (version 1189034): Wire

https://github.com/oxen-io/session-android https://github.com/oxen-io/session-desktop https://github.com/oxen-io/session-ios

This is the correct place to raise feature requests and bug reports: https://github.com/oxen-io/session-desktop/issues

We're at 1.10.8. Please update: https://github.com/oxen-io/session-desktop/releases

Session's reasoning seems much more... cagey. Telling people to recreate their identities themselves sounds a little like the Threema stopgap solution, but it's much sloppier (I can't imagine end users WANT to recreate their account and communicate this to all their contacts via a third party). They're talking about implementing this eventually, but the ticket for doing so was closed right after saying this.

Session F-Droid (version 1.15.4): Encrypted private messenger

Or Briar, Session, Tox, Element/Matrix, Jami...