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.

#InfoSec #FreeSoftware

@rysiek hasn't #Signal demanded people not connect third-party clients to their servers? In fact, any binaries not distributed by them (they refuse to let #FDroid distribute their app). These are only two of many reasons not to support Signal with your unpaid time:

I'd recommend working on a native #SailFish client for #Wire instead. They are a) already close to feature parity with Signal b) actively working towards server>server federation:

@ilpianista @strypey yeah, and looks like Wire cannot work without GCM? Whereas Signal website build APK does work without GCM, AFAIK (been using it on Sailfish before).

@rysiek @ilpianista @strypey

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?


@rysiek @ilpianista @strypey
The fallback solution has been mentioned in the FDroid issue that is linked here above.

@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 @ilpianista

@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?

@strypey a) is the most important thing for me b) fine enough c) not , but I'm thinking to or meanwhile I give a try on Android
@rysiek @Nesaijn

@ilpianista the touchscreen version of #PureOS is GNU/Linux and AFAIK it won't run Android/Linux apps. Not sure about #PlasmaMobile but I'm guessing it's the same.If #Electron doesn't support touchscreen GNU/Linux, there will need to be a native #Wire client developed for it.
@rysiek @Nesaijn

As long as it runs on Linux it should also run on the Librem 5. It would only need to be ported so that the GUI matches the Librem 5.
That's what I understood about the Librem 5.

@ilpianista @rysiek

Sign in to participate in the conversation
Functional Café

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!