On 13/09/2021 16.15, Kim Alvefur wrote:
On Thu, Sep 09, 2021 at 04:29:37PM +0100, Kevin Smith wrote:To summarise what I’ve said before:MUC in MAM kinda sucks, but groupchat doesn’t (necessarily) mean MUC.Sometimes people want groupchat messages in their archive because they want their archive to represent all those messages they received on any client, either for online searching, or offline sync, and MAM is the only mechanism we have for this. If we were to disallow groupchat in MAM completely, it would make existing deployed workflows unavailable. There are countless pitfalls to having MUC (rather than groupchat) in MAM, but prohibiting it just isn’t much of an option. I don’t much like where we are more than anyone else, but it *is* where we are, and I don’t think anyone has the time machine yet to go back and fix MUC preemptively.After discussion with Georg yesterday, I’ve submitted a new version of MAM that uses Dave’s suggested approach.I'm assuming it's this PR here: https://github.com/xsf/xeps/pull/1104/files As a counterproposal; What about a `list-multi` of requested types? Have it default to [chat, normal] or [chat, normal, groupchat] for those that include groupchat by default. Could be extended to PEP notification headline messages, which are similarly awkward.
+1 - Florian
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
