-
@wojtek I do not get how you want to disable local archiving in users MAM by setting an option in a MIX component settings?
Feature mentioned in XEP-0405
urn:xmpp:mix:pam:2#archive
is returned by users local server if it supports archiving MIX messages in MAM. Currently, as we decided to archive everything if not specified that it should not be archived, MIX message are always archived.Do you want a flag in
message-archiving
processor to disable archiving of MIX messages in a user repository? (in MAM processor not in MIX component) Or something else? -
Do you want a flag in message-archiving processor to disable archiving of MIX messages in a user repository? (in MAM processor not in MIX component)
@andrzej.wojcik yes, this.
I created the ticket in MIX project as it somewhat related to MIX
-
@wojtek I wanted to be sure as you wrote:
would be an option in MIX component to disable local archiving
Type |
New Feature
|
Priority |
Minor
|
Assignee | |
Version |
tigase-server-8.2.0
|
Currently, each message ends up in local user MAM archive. For a very busy channels this could lead to significant duplication of entries. One way of dealing with that would be an option in MIX component to disable local archiving of MIX messages (as described in https://xmpp.org/extensions/xep-0405.html#usecase-mam) resulting in user querying MIX MAM archive instead.
(this has some downsides as well: lack of history after leaving the channel and slower querying of MAM over s2s from remote servers)