Re: [Standards] Encrypted Storage (Was: off-server archives with MAM)

2015-04-20 Thread
On 4/18/15 4:47 AM, Kim Alvefur wrote: Further, I don't see why you couldn't have a bot that signs in to your account, enables Carbons and then stores all messages in a local archive, which could then be exposed via MAM to your other clients. Right, that's what I'm suggesting. The harder prob

Re: [Standards] Nonzas: What are they and do we need them?

2015-04-20 Thread
On 4/20/15 12:45 PM, Florian Schmaus wrote: On 20.04.2015 18:22, Christian Schudt wrote: For me personally, the contra-Nonza arguments did not convince me. It appears that nothing in the specification prevents you from using Nonzas after resource binding with BOSH. XEP-206 3. only says "SHOULD

Re: [Standards] Nonzas: What are they and do we need them?

2015-04-20 Thread
On 4/20/15 1:44 PM, Peter Saint-Andre - &yet wrote: On 4/20/15 12:45 PM, Florian Schmaus wrote: On 20.04.2015 18:22, Christian Schudt wrote: For me personally, the contra-Nonza arguments did not convince me. It appears that nothing in the specification prevents you from using Nonzas after res

Re: [Standards] Nonzas: What are they and do we need them?

2015-04-20 Thread Florian Schmaus
On 20.04.2015 17:00, Georg Lukas wrote: > * Florian Schmaus [2015-04-20 15:27]: >> Contra: >> - Messages and IQs could be used instead >> - Can't be used with BOSH > As you pointed out below, they can be used in theory. I just assume that > most implementations will not expect them and might break

Re: [Standards] Nonzas: What are they and do we need them?

2015-04-20 Thread Florian Schmaus
On 20.04.2015 19:40, Philipp Hancke wrote: > Am 20.04.2015 um 06:27 schrieb Florian Schmaus: >> In order to make the following easier, I'd first like to define the term >> Nonza: >> >> A Nonza is every top level XMPP stream element which is not a Stanza. >> (see also [1]). > > http://geekplace.eu/

Re: [Standards] Nonzas: What are they and do we need them?

2015-04-20 Thread Florian Schmaus
On 20.04.2015 18:22, Christian Schudt wrote: > >> For me personally, the contra-Nonza arguments did not convince me. It >> appears that nothing in the specification prevents you from using Nonzas >> after resource binding with BOSH. XEP-206 3. only says "SHOULD contain". >> I also don't see why th

Re: [Standards] Nonzas: What are they and do we need them?

2015-04-20 Thread Dave Cridland
On 20 April 2015 at 18:40, Philipp Hancke wrote: > Am 20.04.2015 um 06:27 schrieb Florian Schmaus: > >> In order to make the following easier, I'd first like to define the term >> Nonza: >> >> A Nonza is every top level XMPP stream element which is not a Stanza. >> (see also [1]). >> > > http://g

Re: [Standards] Nonzas: What are they and do we need them?

2015-04-20 Thread Philipp Hancke
Am 20.04.2015 um 06:27 schrieb Florian Schmaus: In order to make the following easier, I'd first like to define the term Nonza: A Nonza is every top level XMPP stream element which is not a Stanza. (see also [1]). http://geekplace.eu/xeps/xep-nonza/xep-nonza.html#rules and violate those rul

Re: [Standards] Nonzas: What are they and do we need them?

2015-04-20 Thread Matthew Wild
On 20 April 2015 at 17:39, Georg Lukas wrote: > * Matthew Wild [2015-04-20 18:33]: >> > In the XEP-0352 case, "Nonzas" could get lost without resending them >> > upon stream resumption, leaving the client under the impression that >> > it's active, although the server thinks it's inactive. >> Thi

Re: [Standards] Nonzas: What are they and do we need them?

2015-04-20 Thread Georg Lukas
* Matthew Wild [2015-04-20 18:33]: > > In the XEP-0352 case, "Nonzas" could get lost without resending them > > upon stream resumption, leaving the client under the impression that > > it's active, although the server thinks it's inactive. > This can't happen, because new streams are always active

Re: [Standards] Nonzas: What are they and do we need them?

2015-04-20 Thread Matthew Wild
On 20 April 2015 at 17:22, Christian Schudt wrote: > But...: As Georg pointed out, I also think the biggest problem is, that they > are not tracked by XEP-0198. > In the XEP-0352 case, "Nonzas" could get lost without resending them upon > stream resumption, leaving the client under the impressio

Re: [Standards] Nonzas: What are they and do we need them?

2015-04-20 Thread
On 4/20/15 7:27 AM, Florian Schmaus wrote: In order to make the following easier, I'd first like to define the term Nonza: A Nonza is every top level XMPP stream element which is not a Stanza. (see also [1]). Thanks for the fun neologism. :-) Now we just need to figure out what a "wowza" is..

Re: [Standards] Nonzas: What are they and do we need them?

2015-04-20 Thread Christian Schudt
> For me personally, the contra-Nonza arguments did not convince me. It > appears that nothing in the specification prevents you from using Nonzas > after resource binding with BOSH. XEP-206 3. only says "SHOULD contain". > I also don't see why they would introduce "a bunch of conceptual and > imp

Re: [Standards] Nonzas: What are they and do we need them?

2015-04-20 Thread Georg Lukas
* Florian Schmaus [2015-04-20 15:27]: > Contra: > - Messages and IQs could be used instead > - Can't be used with BOSH As you pointed out below, they can be used in theory. I just assume that most implementations will not expect them and might break in subtle ways. IIRC, it required significant r

Re: [Standards] XMPP OAuth2 login at Google

2015-04-20 Thread Anu Pokharel
That’s a relief. I noticed you did this in the newer Adium betas and was wondering what was going on. I guess it’s on my radar to complete on Monal now as well. The gradual movement away from standard XMPP in gtalk is depressing. -Anu > On Apr 20, 2015, at 10:01 AM, Thijs Alkemade wrote: >

Re: [Standards] Carbons as a MAM Subscription (Was: Encrypted Storage)

2015-04-20 Thread Florian Schmaus
On 20.04.2015 13:43, Georg Lukas wrote: > * Georg Lukas [2015-04-18 11:42]: >> I really dislike (ab)using carbons as a MAM pseudo-subscription. > > Another case in point: Carbons are not reflected to the sender, so if > you send a message, you have no way (yet) to know its archive ID. Right, I a

Re: [Standards] XMPP OAuth2 login at Google

2015-04-20 Thread Thijs Alkemade
> On 20 apr. 2015, at 10:15, Thijs Alkemade wrote: > > [Reviving a very old thread] > > It looks like today is going to be the day Google shuts down ClientLogin [1], > and with that, SASL PLAIN [2]. This might be the final nail in the coffin of > XMPP support for Google Talk, as I fear few clie

[Standards] Nonzas: What are they and do we need them?

2015-04-20 Thread Florian Schmaus
In order to make the following easier, I'd first like to define the term Nonza: A Nonza is every top level XMPP stream element which is not a Stanza. (see also [1]). To my best knowledge, Nonzas which are exchanged after resource binding, are currently used in xep198 and xep352. A recently propos

[Standards] XEP-0082 errounously states that CCYY has four digits

2015-04-20 Thread Florian Schmaus
Dear authors for XEP-0082: XMPP Date and Time Profiles, please consider the attached patch to clarify that the 'CCYY' part may consists of more then four digits and may be prefixed with a minus sign, as specified by 'xs:dateTime' in http://www.w3.org/TR/xmlschema-2/#dateTime. Thanks Florian com

Re: [Standards] Standards Digest, Vol 137, Issue 19

2015-04-20 Thread 极简吴剑
1. Re: off-server archives with MAM (Goffi) 2015-04-19 20:00 GMT+08:00, standards-requ...@xmpp.org : > Send Standards mailing list submissions to > standards@xmpp.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.jabber.org/mailman/listinfo/standards > or,

[Standards] Carbons as a MAM Subscription (Was: Encrypted Storage)

2015-04-20 Thread Georg Lukas
* Georg Lukas [2015-04-18 11:42]: > I really dislike (ab)using carbons as a MAM pseudo-subscription. Another case in point: Carbons are not reflected to the sender, so if you send a message, you have no way (yet) to know its archive ID. Basically, we need to ensure two things here: a) determine

Re: [Standards] XMPP OAuth2 login at Google

2015-04-20 Thread Thijs Alkemade
[Reviving a very old thread] It looks like today is going to be the day Google shuts down ClientLogin [1], and with that, SASL PLAIN [2]. This might be the final nail in the coffin of XMPP support for Google Talk, as I fear few clients have implemented X-OAUTH2. We have an update in beta for Adiu