If anyone knows #Go and is looking for a project to help out with, Go-based #Signal protocol implementation library and a native #SailfishOS Signal client using it are in dire need of love:
Yes, I also prefer truly decentralized protocols, but Signal is where it's at currently with a lot of people, and it's way better than other popular options... So, we need independent clients.
Wire does look for Google Play Services but has another solution for the case that it can`t find it. It also works without it.
Wire does not distribute it`s app on FDroid but on their website.
But doesn`t Wire still store unencrypted Metadata on their server or has it been solved already?
@Nesaijn according to comments in the issue you linked #Wire are working on reducing stored metdata with in their work with the #MLS protocol. #Signal requires a phone number and a mobile device, and does its best to enslave its users on Android to goOgle Play Store, all of which create potential metadata leaks.
@rysiek AFAIK this is still an issue with the official #Wire client on Android but:
a) they are happy to let users *use* their software freedom by connecting to their servers with unofficial clients. #Signal are not
b) they want to get their app into #FDroid. Signal have explicitly denied F-Droid permission to distribute independently compiled builds under the name Signal.
c) are any of these Android issues relevant to building a client for #Sailfish?
functional.cafe is an instance for people interested in functional programming and languages.