I just double checked: - twitter: moxie wrote "it's the same code" - github: GPL3 license That means that Whatsapp is going to open source their app: this is awesome! Marco
ah, now that actually means something, then. If WhatsApp's client is auditable then it's great news. Otherwise, no matter what convolutions the trustworthy *part* of the code undergoes to ensure end-to-end, the rest can just clone the keys and post home. On 19 November 2014 09:15:04 GMT+00:00, Marco Pozzato <mpodroid@gmail.com> wrote:
I just double checked:
- twitter: moxie wrote "it's the same code" - github: GPL3 license
That means that Whatsapp is going to open source their app: this is awesome!
Marco
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Though bear in mind that if Moxie had all code contributors assign copyright to him, then he has the right to waive the GPL when using that code with closed partners. Only if contributors keep their rights and publish in GPL do you iron-clad the GPL into the codebase, because now to sidestep your commitment to freedom you must go back and re-implement all the code whose copyright belongs to a contributor. So, GPL or no, there is scope for Moxie to renege and offer alternate licensing on OWS code to WhatsApp, but only if contributor code is either excised or copyright transferred. On 19 November 2014 09:15:04 GMT+00:00, Marco Pozzato <mpodroid@gmail.com> wrote:
I just double checked:
- twitter: moxie wrote "it's the same code" - github: GPL3 license
That means that Whatsapp is going to open source their app: this is awesome!
Marco
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
The copyright holder can always dual-license it. In the case of text secure it's a bit more complicated, but still the CLA allows OWS to dual-license the code. So I wouldn't expect anything.
So their is a CLA? Forget end to end security, then. On 19 November 2014 09:35:35 GMT+00:00, CodesInChaos <codesinchaos@gmail.com> wrote:
The copyright holder can always dual-license it. In the case of text secure it's a bit more complicated, but still the CLA allows OWS to dual-license the code. So I wouldn't expect anything.
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
(Goddammit typos, I'm not actually illiterate I promise) On 19 November 2014 09:49:53 GMT+00:00, "Cathal (Phone)" <cathalgarvey@cathalgarvey.me> wrote:
So their is a CLA? Forget end to end security, then.
On 19 November 2014 09:35:35 GMT+00:00, CodesInChaos <codesinchaos@gmail.com> wrote:
The copyright holder can always dual-license it. In the case of text secure it's a bit more complicated, but still the CLA allows OWS to dual-license the code. So I wouldn't expect anything.
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
On 11/19/2014 11:15 AM, Marco Pozzato wrote:
I just double checked:
* twitter: moxie wrote "it's the same code" * github: GPL3 license
That means that Whatsapp is going to open source their app: this is awesome!
Probably not. Open Whispers has the right to dual license the code to any OSI-approved license (eg. BSD) for a 3rd party. https://whispersystems.org/cla/
"This license is for your protection as a Contributor" What a load of shite. Here, have my copyright. I'm safer without it, I could slip on it or something. On 19 November 2014 10:06:46 GMT+00:00, Nikos Roussos <comzeradd@fsfe.org> wrote:
On 11/19/2014 11:15 AM, Marco Pozzato wrote:
I just double checked:
* twitter: moxie wrote "it's the same code" * github: GPL3 license
That means that Whatsapp is going to open source their app: this is awesome!
Probably not.
Open Whispers has the right to dual license the code to any OSI-approved license (eg. BSD) for a 3rd party. https://whispersystems.org/cla/
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
participants (4)
-
Cathal (Phone) -
CodesInChaos -
Marco Pozzato -
Nikos Roussos