You are right, indeed. I was misinterpreting "timer setting" etc. and
jumped to conclusions. Ignore me ;-)
On Wed, 2018-06-06 at 18:31 +0200, Jonas Wielicki wrote:
> On Mittwoch, 6. Juni 2018 13:13:23 CEST Marcel Waldvogel wrote:
> I understand that time synchronization is important, but I
>
On Mittwoch, 6. Juni 2018 18:42:47 CEST Dave Cridland wrote:
> I really don't want to have any IQ based flows prior to login if possible -
> with my server-dev hat on, I find it worrying to have to do deep inspection
> of IQ stanzas during pre-auth.
With my client hat on, I agree 100%.
But SASL2
On Wed, Jun 6, 2018, at 11:30, Jonas Wielicki wrote:
> I see that the IQ-based pre-auth flow is an issue, and integrating this in
> SASL2 or something is probably the better way to handle this. However, this
> also needs to work pre- or during IBR in some way.
Yes, this makes sense; I can see
On 6 June 2018 at 17:30, Jonas Wielicki wrote:
> On Mittwoch, 6. Juni 2018 16:52:27 CEST Sam Whited wrote:
> > I'm not af an of how this one was done. -1 for now. I'd like to discuss
> how
> > this can be done better though; it seems to me that it would fit very
> well
> > as part of extensible
On Mittwoch, 6. Juni 2018 13:13:23 CEST Marcel Waldvogel wrote:
> I understand that time synchronization is important, but I would
> recommend not to burden XMPP with timer synchronization. We do have a
> reliable NTP infrastructure including pool.ntp.org; mobile devices
> often have the
On Mittwoch, 6. Juni 2018 16:52:27 CEST Sam Whited wrote:
> I'm not af an of how this one was done. -1 for now. I'd like to discuss how
> this can be done better though; it seems to me that it would fit very well
> as part of extensible IBR and/or SASL2.
I agree that IBR or SASL2 or whatever
On Wed, May 30, 2018, at 19:22, Tedd Sterr wrote:
> 3) Proposed XMPP Extension: Terms of Services -
> https://xmpp.org/extensions/inbox/tos.html
>
> Kev: +1 (don't like this much, but not blocking it)
> Daniel: [to vote on-list]
> Georg: +1 (it's great to have a machine-readable way to link the
On 31 May 2018 at 01:22, Tedd Sterr wrote:
> http://logs.xmpp.org/council/2018-05-30/#15:00:13
>
> *1) Roll Call* - https://en.wikipedia.org/wiki/Roll_Call
> Present: Kev, Daniel, Georg, Sam
> Better things to do: Dave
>
> *2) Isn't it nice that Tedd Sterr does the minutes?*
> There are no
2018-05-31 2:22 GMT+02:00 Tedd Sterr :
> 3) Proposed XMPP Extension: Terms of Services -
> https://xmpp.org/extensions/inbox/tos.html
>
> Kev: +1 (don't like this much, but not blocking it)
> Daniel: [to vote on-list]
> Georg: +1 (it's great to have a machine-readable way to link the ToS; not
>
I understand that time synchronization is important, but I would
recommend not to burden XMPP with timer synchronization. We do have a
reliable NTP infrastructure including pool.ntp.org; mobile devices
often have the capability to synchronize to other time sources (mobile
phone infrastructure,
On 6 Jun 2018, at 01:35, Tedd Sterr wrote:
> > 2) Isn't it nice that Tedd Sterr does the minutes?
>
> Come on, you need a new joke now - this one started wearing thin weeks ago
How well do you know Dave? :)
/K
___
Standards mailing list
Info:
ср, 6 июн. 2018 г. в 11:08, JC Brand :
> Is this an extension/modification of XEP-0045, or is this a completely
> different groupchat
> protocol?
Completely different. XEP-0045 is beyond repair.
> > * Group chat server resends messages to everyone but sender with
> >special
On Sun, Jun 03, 2018 at 07:30:48PM +0500, Ненахов Андрей wrote:
>To whom it may concern, we're working on group chat solution for XMPP.
>It is quite a simple solution that we feel is good enough to counter most
>issues of XEP-0045.
Is this an extension/modification of XEP-0045, or is
13 matches
Mail list logo
