Re: [Standards] NEW: XEP-0401 (Easy User Onboarding)

On Mittwoch, 21. Februar 2018 19:42:19 CET Georg Lukas wrote: > * Jonas Wielicki [2018-01-25 15:57]: > > > However, then we need to define how the client can determine whether > > > this Data Form is a PREAUTH compatible form, and whether the user is > > > still required to

Re: [Standards] undefined state in XEP-0050

Le mercredi 21 février 2018, 19:50:17 CET Florian Schmaus a écrit : > But this is unlikely to change ever. So here is how I understand it: > > - 'execute' always gets you into the next stage, and iff 'next' is an > allowed action, then 'execute' is equivalent to 'next', or otherwise it > is

Re: [Standards] undefined state in XEP-0050

On 06.08.2015 17:42, Goffi wrote: > G'day, > > there is a little issue with XEP-0050: in section 3.4 bullet 3, it's is > said that when the element is present: > > - The action "execute" is always allowed, and is equivalent to the > action "next". > - The "next" action is typically the

Re: [Standards] NEW: XEP-0401 (Easy User Onboarding)

* Jonas Wielicki [2018-01-25 15:57]: > > However, then we need to define how the client can determine whether > > this Data Form is a PREAUTH compatible form, and whether the user is > > still required to add more content. > > This can easily be done. Just specify the field

Re: [Standards] XEP-0198: Stream should be closed when 'h' value is to high

Am Mittwoch, den 21.02.2018, 16:17 + schrieb Kevin Smith: > On 21 Feb 2018, at 13:21, Jonas Wielicki wrote: > > > > On Mittwoch, 21. Februar 2018 11:57:56 CET Kevin Smith wrote: > > > On 21 Feb 2018, at 09:41, Jonas Wielicki > > > wrote: > > > > On

Re: [Standards] MAM Corner Cases: MUC-PMs and Self-Messages

On Feb 21, 2018 19:05, "Georg Lukas" wrote: Hi, Philipp H. pointed out an interesting issue today: MUC-PMs are sent by a MUC to all joined client full-JIDs, so if you are joined to a MUC with two devices, your account will see two copies of the messages. Your MAM archive is also

[Standards] MAM Corner Cases: MUC-PMs and Self-Messages

Hi, Philipp H. pointed out an interesting issue today: MUC-PMs are sent by a MUC to all joined client full-JIDs, so if you are joined to a MUC with two devices, your account will see two copies of the messages. Your MAM archive is also going to store two copies of them, with different MAM-IDs,

Re: [Standards] XEP-0198: Stream should be closed when 'h' value is to high

On 21 Feb 2018, at 13:21, Jonas Wielicki wrote: > > On Mittwoch, 21. Februar 2018 11:57:56 CET Kevin Smith wrote: >> On 21 Feb 2018, at 09:41, Jonas Wielicki wrote: >>> On Mittwoch, 21. Februar 2018 10:32:37 CET Kevin Smith wrote: At first glance,

[Standards] Council minutes 2018-02-21

Room logs: http://logs.xmpp.org/council/2018-02-21/ 1) Roll call Kev, Sam, Daniel, Georg present. Dave sends apologies. 2) Date of next meeting 2018-02-28 16:00Z 3) Any other business Georg asked if -71 was deprecated yet. It’s not, but there’s a vote underway. Fini

Re: [Standards] XEP-0198: Stream should be closed when 'h' value is to high

On Mittwoch, 21. Februar 2018 11:57:56 CET Kevin Smith wrote: > On 21 Feb 2018, at 09:41, Jonas Wielicki wrote: > > On Mittwoch, 21. Februar 2018 10:32:37 CET Kevin Smith wrote: > >> At first glance, its seems to me like this can only happen when an > >> entity’s > >> 198

Re: [Standards] XEP-0198: Stream should be closed when 'h' value is to high

On 21 Feb 2018, at 09:41, Jonas Wielicki wrote: > > On Mittwoch, 21. Februar 2018 10:32:37 CET Kevin Smith wrote: >> At first glance, its seems to me like this can only happen when an entity’s >> 198 support is broken in some way. If that’s the case, would we expect the >>

Re: [Standards] XEP-0198: Stream should be closed when 'h' value is to high

On Mittwoch, 21. Februar 2018 10:32:37 CET Kevin Smith wrote: > At first glance, its seems to me like this can only happen when an entity’s > 198 support is broken in some way. If that’s the case, would we expect the > same entity to reconnect and do the same thing again? If so, is it better > to

Re: [Standards] XEP-0198: Stream should be closed when 'h' value is to high

Sorry I’m late to the party. > On 7 Feb 2018, at 09:11, Dave Cridland wrote: > > On 7 February 2018 at 08:55, Christian Schudt wrote: >> This would follow the "Principle of Least Surprise", since terminating the >> stream may seem a bit harsh for the