[Standards] XEP-0313 for transports

Jonas Schäfer jonas at wielicki.name
Wed Mar 4 15:58:22 UTC 2020



4 Mar 2020 4:36:08 pm Kevin Smith :

> On 26 Feb 2020, at 17:24, Jonas Schäfer < jonas at wielicki.name [mailto:jonas at wielicki.name] > wrote:
>
> >
> > On Mittwoch, 26. Februar 2020 16:40:06 CET Ivan Vučica wrote:
> >
> > > Hi,
> > >
> > > Sometimes, protocols backing transports may support querying for an
> > > archive similar to how it's done with XEP-0313.
> > >
> > > tl;dr Can querying archives on non-own, non-MUC, non-pubsub JID for
> > > 1:1 chats be standardized? Can it be standardized that server
> > > implementations don't have to support date-based queries?
> > >
> > >
> > >
> > > 1. XEP-0313 is specified for archives maintained by the user's own
> > > server. Section 3.3 doesn't specify that a client can query a remote
> > > JID for the archive, which would be useful for transports. It does
> > > specify it for MUC and pubsub, but not for 1:1.
> > >
> > > Here I'm mainly interested: Are there clients that would query a
> > > remote JID for the archive today, despite XEP-0313 not requiring
> > > servers nor clients to support this? Under which conditions would they
> > > do this?
> > >
> >
> > Ugh. No, I don’t think any client would query a remote JID for 1:1 archives.
> >
>
> Why not? MAM’s just a mechanism for querying archives for messages, surely it shouldn’t matter where the archive is?

I meant "right now as it stands".

--
Jonas Schäfer
This was sent from mobile, and I'm not good with those. Sorry for brevity and such.



More information about the Standards mailing list