Here's the Telegram iOS code by the way: https://github.com/peter-iakovlev/Telegram
Re:Viber adds end-to-end encryption
by andrey_utkin on Tuesday April 19, 2016 @09:00AM
(#11526589)
> I mean, sure, there could be "Whatsapp clones" (aren't there already?!)
Sounds funny if you consider that Whatsapp itself is just a branded deployment of FOSS XMPP server Ejabberd, with feature of federation taken away. Plus a client app implementation, of course.
That is only possible because Ejabberd doesn't use the AGPL license.
Come on, it would definitely still be possible with AGPL code. What brought people to whatsapp is its ubiquity and the fact that it just works, and what keeps them from going elsewhere is the inevitable network effect.
Nothing in the AGPL prevents either from occurring.
I think you are misunderstanding jeena. If ejabberd were AGPL, then a fork/a instance of it like Whatsapp would be legally obliged to open up their code as well.
No idea whether the assumption is true that Whatsapp is just a branded deployment.
I still don't understand how opening up the codebase would prevent them from being successful.
As the countless messaging apps out there demonstrate, the value of communication apps lies in the network they build. If they provide a decent UX, and successfully bootstrap a network large enough, it wont matter if their code is open.
I don't think that was an argument against that. At least I agree. The situation is only possible because the AGPL is not used for the free component, but Whatsapp should have no problem opening up their code.
And, I've been using Viber longer than I knew WhatsApp existed. Just saying...
Re:Viber adds end-to-end encryption
by venomsnake on Tuesday April 19, 2016 @09:25AM
(#11526730)
Wireshark,xposed + some creativity and you have your own E2E encrypted solution with OOB keys. For any messenger. It is not done, because there is no demand.
Would it be possible to explain the reasoning of the workflow/toolchain you're suggesting?
Re:Viber adds end-to-end encryption
by venomsnake on Tuesday April 19, 2016 @04:07PM
(#11529846)
wireshark to reverse the protocol. xposed to rewrite the classes required on android.
you replace Whatsapp.sendMessage(string,Jonny) with WhatsApps.sendMessage(EncryptString(string,Jonny),Jonny)
And EncryptString taps into your keystore to find jonny's key.
I mean, sure, there could be "Whatsapp clones" (aren't there already?!), but wouldn't Whatsapp still benefit from the phone number user base it has, thus maintaining a certain lock-in on its users from which it already benefits?