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.
@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:
@strypey yeah, I am more interested in Briar (time to go full p2p decentralized).
I need Signal for work. It took 3 years to move 200+ journalists to Signal, I don't have 3 more years to now move them to Wire, unless Signal really fscks up big time.
> I need Signal for work.
Fair enough, but that's no reason to encourage people to do unpaid work for them. Why support #SailFish anyway? Hardly anyone uses it and #Jolla refuse to release all the source code for their UI under free licenses.
> unless Signal really fscks up big time.
Did you read OP of the first link I posted?
> that's no reason to encourage people to do unpaid work for them.
Moxie fights the idea of independent clients, so this is far from working *for them*. In fact, it seems to be the opposite.
> Why support Sailfish?
Because it's the only usable mobile OS that is so open and comes with actual support.
> Did you read OP of the first link I posted?
Yes, and I agree with most of it. But I need to communicate with people where my choices are Signal or Viber/Telegram/Whatsapp.