[Standards] XEP-0313: Treatment of type=groupchat in user archive with or without <store/> hint

Georg Lukas georg at op-co.de
Fri Nov 24 16:36:53 UTC 2017

* Kevin Smith <kevin.smith at isode.com> [2017-11-23 18:33]:
> On 23 Nov 2017, at 17:11, Daniel Gultsch <daniel at gultsch.de> wrote:
> > For me it doesn't ever make sense to store type=groupchat messages in
> > the user archive.

I agree with that. We shouldn't make MAM more complicated, and we should
specify that MAM should not ever return type=groupchat messages when
queried (or maybe even that it should not store them).

> The main use case for having gc messages in the archive is “I remember
> I saw someone say something interesting about X, so now I’m going to
> search my archive for X to find it”, which really needs to have all
> the messages you’ve seen available, rather than splitting them between
> multiple sources, some of which won’t support MAM.

For search, I think it would be better to define a separate mechanism
where the client can query the archive, and the archive can (if it wants
to) search whatever messages it has stored internally, but not return
those messages to normal MAM queries.

I really can't see a search implementation that first downloads the full
archive to the client and then searches locally.

|| http://op-co.de ++  GCS d--(++) s: a C+++ UL+++ !P L+++ !E W+++ N  ++
|| gpg: 0x962FD2DE ||  o? K- w---() O M V? PS+ PE-- Y++ PGP+ t+ 5 R+  ||
|| Ge0rG: euIRCnet ||  X(+++) tv+ b+(++) DI+++ D- G e++++ h- r++ y?   ||
++ IRCnet OFTC OPN ||_________________________________________________||
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20171124/bcdd7aa0/attachment.sig>

More information about the Standards mailing list