ralphmGe0rG, and for what it is worth, Wire sued OWS, and then there was a settlement. Also, Wire's stuff is still GPL3.
jonas’pep., according to https://medium.com/@wireapp/axolotl-and-proteus-788519b186a7, I think so
jonas’> Like everyone else in the cryptographic community, our team obviously had access to OWS’ GPL’d Java reference implementation online.
jonas’well, ok, maybe not
pep.the article does mention the gpl'd code yeah
ralphmThe thread I linked also has Moxie in it somewhere.
ralphmIn any case, you'll see that SilentCircle pulled libsalamander in favour of libzina.
MattJThe reply from Moxie in that thread basically says they only care about the trademark
jonas’(which is part of the evil constants)
MattJBut even GPL doesn't save you from that
jonas’I wonder if that was all planned out from the beginning or just a lucky coincidence.
ralphmThe protocol includes constants with 'signal' in them, no? It seems to me that OWS considers any protocol-compatible implementation to be a derivative work.
jonas’ralphm, WhisperSystems even
ralphmof course XMPP has literal occurances of 'jabber', but at least there's an arrangement with the XSF for this.
dwdralphm, As I recall, that caused a lot of wrangling in the IETF.
dwdralphm, Not least the name of the protocol changed.
ralphmdwd: I thought that XMPP was actually proposed by Jabber, Inc.
fipponah, i think the ietf concluded that having a protocol and a trademark was not going to work. smart. I am looking at you, w3c+webrtc...
dwdI don't know where the name came from. I do know that the IETF got very concerned about a protocol name being trademarked.
ralphmdwd: interestingly, the first draft (https://tools.ietf.org/html/draft-ietf-xmpp-core-00) had this notice:
1.4 Intellectual Property Notice
This document is in full compliance with all provisions of Section 10
of RFC 2026. Parts of this specification use the term "jabber" for
identifying namespaces and other protocol syntax. Jabber[tm] is a
registered trademark of Jabber, Inc. Jabber, Inc. grants permission
to the IETF for use of the Jabber trademark in association with this
specification and its successors, if any.
dwdDear Editors. I'm sorry-not-sorry.
ralphmI tried to look at the old xmppwg mail archives, but it seems that our mailman doesn't show them (anymore).
ralphmMattJ, are they still there?
ralphm(they used to be here: https://mail.jabber.org/pipermail/xmppwg/)
dwdGuus, You might care about this: https://github.com/xsf/xeps/pull/883
ZashI didn't know this
GuusThanks Dave 🙂
ZashWhat has Dave done now?
GuusBe a gentleman.
ralphmZash, yeah, the xmppwg mailinglist (first WG) was initially hosted by the JSF.
dwdAnother two ProtoXEPs. Given my current success rate, I'm not sure why I bother, but still.
MattJdwd: thanks, that's an item off my to-do :)
MattJdwd: for what it's worth my plan was to spec two fields, a universal "plain" search and an "advanced" variant that is implementation/deployment-specific but includes a slot for the server to provide some (localized) help text that clients could display to users
MattJSee the popup when you enter the search box in Slack for example
jonas’with the emoji?
ralphmInterestingly around that time also a lot of e2e discussion (for RFC 3923)
fipporalphm: IIRC peter once said that he wasn't aware of any implementations of 3923. It was more of a mandated checkbox because of the IMPS-requirements
ralphmIt was, but it still had a lot of discussion
ralphmdwd: small typo in PR 883, reviewed.
dwdAh, crap. Yep.
Dele (Mobile)has left
Dele (Mobile)has joined
pep.https://xmpp.org/about/xsf/mission Is it possible to find context around this? I've been skimming through the member list without success. Added in a71bc1df7a100a72b9e840c2a7308668fa385e32 on Sun Jul 26 23:41:33 2015 -0700 by Adam Brault
pep.https://xmpp.org/about/xsf/mission Is it possible to get context around this? I've been skimming through the member list without success. Added in a71bc1df7a100a72b9e840c2a7308668fa385e32 on Sun Jul 26 23:41:33 2015 -0700 by Adam Brault
pep.Reading old threads makes me feel like we're a broken record
pep.https://mail.jabber.org/pipermail/members/2014-November/007920.html "Abstaining on XSF ballots"
pep.Ah, there's https://mail.jabber.org/pipermail/members/2014-November/007932.html "Goals for the XSF board". Not sure if that's what lead to the mission statement, but that's probably worth reading anyway
ralphmpep., in 2015 the entire website was redone
ralphmThe origin of this page is in 2007.
ralphmI.e. that's how far I've traced it back for now.
Link Mauvehas joined
ralphmBecause I think it is even older, and Jan 2007 was an earlier website overhaul
ralphmI.e. this is when our site moved to xmpp.org
ralphmpep., this page used to be on jabber.org, and virtually hasn't changed since the fall of 2003.