Or, if this would take too long, a couple other options:
- Ship Signal as the default sms app only; if people want to enable encrypted messaging they can install the Gapps pico-package and then register with Signal (prompt them to do this?).
- Ship a community-maintained fork that supports websocket.
________________________________
From: whispersystems-***@lists.riseup.net [whispersystems-***@lists.riseup.net] on behalf of Leo Francisco [***@boywithwings.co.uk]
Sent: Friday, January 15, 2016 9:18
To: ***@lists.riseup.net
Subject: Re: [whispersystems] Signal on Cyanogen Mod without gapps
Would it be too crazy to suggest that at some point in the future it would be amazing to make Signal the default messaging app on Cyanogen Mod?
Assuming for example that Signal will eventually work without GCM via websockets and loads of other hypothetical things happened (plus reaching some sort of CM community consensus).
On 04/01/16 08:16, Boskote wrote:
On 04/01/16 01:16 AM, Josh wrote:
Slightly off-topic, but does anyone know if CyenogenMod still integrates
with Signal automatically?
A single number cannot be registered with both WhisperPush and Signal at the same time. In theory they are supposed to be able to communicate. I haven't tried it myself, though as of mid-2015 communication between WP and TextSecure/Signal seems to have had problems:
https://www.reddit.com/r/cyanogenmod/comments/31u0wb/does_whisperpush_work_with_signal/
https://github.com/WhisperSystems/Signal-Android/issues/3659
Also, even if communication between Signal and WhisperPush were working, the usability of WP seems questionable. There were definitely major problems with it in early 2014, when these posts were made to the list:
https://lists.riseup.net/www/arc/whispersystems/2014-03/msg00094.html
" Moxie mentioned several times that the CM guys are completely
responsible for the WhisperPush implementation. Thus you should
probably point that out in their github:
https://github.com/CyanogenMod/android_external_whispersystems_WhisperPush/issues
I also think that not distinguishing between encrypted and unencrypted
communication is a fatal flaw. But unfortunately the whole WhisperPush
implementation seems rather unusable and not well maintained."
https://lists.riseup.net/www/arc/whispersystems/2014-04/msg00012.html
" I am aware that OWS are not responsible for the further development of
WhisperPush. But it's the single biggest source of people who might use
the TS V2 protocol and basically unusable right now. Everyone with CM I
know has disabled it, some using TS instead.
Even the most basic things don't work:
- There is no indicator if the person you are talking to uses WP/TS.
- There is no SMS-fallback, but it works as a transparent middleware,
making it basically impossible to write an SMS to someone registered
with WP.
- No picture/media support
And because of the missing indicator you might not even know why
somebody "doesn't answer" your "SMS" when they actually just stopped
usig WP."
And unfortunately there doesn't seem to have been much substantive work done on WP since then.