On Fri, Apr 03, 2020 at 09:51:37PM +0100, Matthew Wild wrote:
> The core of XEP-0313 that remains has actually gained some new features
> that were repeatedly requested by people to help with implementation
> issues. Importantly the namespace has not been bumped, but servers that
> support the new
On Wed, Jun 19, 2019 at 01:04:07PM +0200, Kim Alvefur wrote:
> Feature negotiation doesn't work becasue since the introduction of
> Carbons and MAM you no longer have any idea which clients will receive
> anything you sendwhich will receive anything you send.
When is it that you could determine
I hope people don't feel I'm derailing the conversation.
All I'm saying is that using the EXTERNAL authentication described as in the
original proposal has interesting properties, but it might be overloading
the meaning of EXTERNAL when in fact there is a different, standardized
mechanism with
On Thu, Feb 14, 2019 at 03:33:44PM +0500, Ненахов Андрей wrote:
> Actually, getting rid of a master passwords is exactly what our server team
> is working on. Here's what design features we're implementing:
> 1) on connect with login/password device is issued a token, and a session
> stops. Device
On Mon, Jan 07, 2019 at 11:30:26AM +0300, Evgeny wrote:
> On Mon, Jan 7, 2019 at 10:44 AM, Goffi wrote:
> > Is there any implementation in the wild which would have issue with node
> > order?
>
> Sure, any clustered database will have issues with
> such naive approach: after partitioning during
On Tuesday, August 05, 2014 03:21:11 PM XMPP Extensions Editor wrote:
Additionally, the protocol is used to negotitate whether the receiving
Is the 'negotitate' intentional?
