On Wed, Jul 14, 2021 at 02:13:19PM +0100, Matthew Wild wrote:
On Wed, 14 Jul 2021 at 12:12, Matthew Wild wrote:
I think your point and Kev's are somewhat related. The current
proposal does not allow for preservation of explicit subscriptions or
affiliations. I think today's reality is that
On Wed, 14 Jul 2021 at 12:12, Matthew Wild wrote:
> I think your point and Kev's are somewhat related. The current
> proposal does not allow for preservation of explicit subscriptions or
> affiliations. I think today's reality is that everyone is doing full
> pubsub on the account JID, and it
On Tue, 29 Jun 2021 at 13:40, Kim Alvefur wrote:
>
> Hi,
>
> On Wed, Jun 02, 2021 at 04:59:40PM +0100, Matthew Wild wrote:
> >I've prepared an update that adds some of the missing features:
> > - PEP nodes (configuration and items)
>
> What about explicit subscriptions and affiliations relevant?
Hi,
On Wed, Jun 02, 2021 at 04:59:40PM +0100, Matthew Wild wrote:
I've prepared an update that adds some of the missing features:
- PEP nodes (configuration and items)
What about explicit subscriptions and affiliations relevant? While not
strictly required for basic PEP, there are
Thanks Matt, a couple of comments:
On not namespace bumping:
227 already said you had to cope with unexpected elements, so simply including
the new elements in their new namespaces seems ok to me. (Although this may
generate warnings. *shrug*)
PEP:
Do you mean PEP as in 163, or full
Hi list,
On Mittwoch, 23. Juni 2021 20:05:20 CEST Matthew Wild wrote:
> On Wed, 23 Jun 2021, 17:21 Guus der Kinderen,
>
> wrote:
> > Should we consider introducing a change to the namespace as used in the
> > portable data, to more explicitly handle the changes in format? I'm aware
> > that you
Hi,
Thanks for your feedback!
On Wed, 23 Jun 2021, 17:21 Guus der Kinderen,
wrote:
> Should we consider introducing a change to the namespace as used in the
> portable data, to more explicitly handle the changes in format? I'm aware
> that you mainly introduced new elements, and the one
Hi Matt,
Thanks for reviving this thing. It was indeed pretty outdated.
Openfire has an implementation too, although I'm not aware if it was ever
tested against other servers.
Should we consider introducing a change to the namespace as used in the
portable data, to more explicitly handle the
Hi folks,
This somewhat forgotten XEP used to be the way to migrate data between
XMPP services. Unfortunately it didn't keep up with the times, and
many servers gained tools for importing directly from the native
formats of other servers (Prosody has an ejabberd importer, ejabberd
has a Prosody
