Michal Krenek (Mikos)

@f41c0r It's standard ZRTP, but they use their own simple signaling protocol, not XMPP or SIP. But with key continuity check disabled after switch from RedPhone to Signal, there is...

@art1fa This is strange, I am now using WebSocket build of TextSecure daily on Nexus 4 (with original Google ROM) and I don't see it in battery stats at all...

I am using it both on WiFi and 3G (but WiFi use is much more frequent, about 80% of time). This is on latest Android 5.1.1

Just my two cents... A) this repo _is_ for now the source for LibreSignal. I have not added any feature by myself to that build yet, only presented pull request...

I have already thought about creating independent LibreSignal repository on GitHub. Mainly because I want to implement back ZRTP key continuity check (see [Issue #44 - ZRTP key continuity check...

Well, I would actually prefer if LibreSignal repository would be completely independ (and not limiting new features). JavaJens repository can stay as upstream with basic WebSocket support. My secret dream...

In worst case scenario we can make sure that requests from WebSocket fork closely mimic requests from Signal Desktop app for Chrome (which also uses WebSocket). This way OWS wouldn't...

That won't work, 1.) not everyone is from US juristidiction, 2.) they would completely alienate whole opensource world and make everyone suspicious about their motives, 3.) there were always third-party...

@f41c0r SAS is _Short Authentication String_, shared value (those two words displayed on screen while calling with RedPhone/Signal) which both communicating parties should verbally cross-check. With key continuity, it is...

@h-2 This is really important basic security feature, without it even cSipSimple (or any other SIP client which supports ZRTP) is much more secure than Signal.