Allow how MUC PMs are stored to be configurable #147
Comments
|
Two new properties to be introduced, both take boolean values, both default to
|
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Dec 11, 2020
…able Historically, Private Messages sent through MUC rooms are stored as if they were one-on-one messages (in the personal archives of users). With igniterealtime#133 these PMs are now also stored in the MUC archive. Existing functionality might depend on these messages to be stored in the personal archives, or might break when these messages start showing up in the MUC archives. The changes in igniterealtime#133 retain the old functionality, but also adds the messages to the MUC archives (there's duplication now). Configuration options should be made available to control this behavior. Two new properties to be introduced, both take boolean values, both default to true: - conversation.roomArchiving.PMinPersonalArchive - conversation.roomArchiving.PMinRoomArchive
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Historically, Private Messages sent through MUC rooms are stored as if they were one-on-one messages (in the personal archives of users). With #133 these PMs are now also stored in the MUC archive.
Existing functionality might depend on these messages to be stored in the personal archives, or might break when these messages start showing up in the MUC archives.
The changes in #133 retain the old functionality, but also adds the messages to the MUC archives (there's duplication now).
Configuration options should be made available to control this behavior.
The text was updated successfully, but these errors were encountered: