#763 Chatstates are saved in MAM

Reporter lovetox
Owner Zash
Created
Updated
Stars ★ (1)
Tags
  • Compliance
  • Status-Fixed
  • Milestone-0.10
  • Type-Defect
  • Priority-Medium
  1. lovetox on

    Please provide a snippet of the part of the specification which we violate if possible: A user archive is anticipated to provide the user with the ability to access their prior conversations. To this end, a server SHOULD include in a user archive all of the messages a user sends or receives of type 'normal' or 'chat' that contain a <body> element. A server SHOULD also include messages of type 'groupchat' that have a <body>, but where such history is accessible through another method (e.g. through an archive on the MUC JID), a server MAY exclude these from the archive. A server MAY include additional non-conversation messages. A server MAY include messages of type 'headline', but this is not generally suggested. Please provide a link to the specification: http://xmpp.org/extensions/xep-0313.html#sect-idp1638784 Now i know prosody does strictly speaking NOT violate that spec. but it does save messages (Chatstates) which have no body, and its not suggested by the XEP for good reason. So it would be good to make the default behaviour not save Chatstates. The other Option is, that all Clients that support that, would have to add no-store hints to stanzas that are not really rare. Because requesting MAM for a prosody user results in a lot of unnecessary Messages if Clients dont add that hint.

  2. lovetox on

    additionally i would link this issue: https://prosody.im/issues/issue/619

  3. Zash on

    I would argue that this is a duplicate of #750 and that the rules for what to store and what not to store have become pretty complicated and will need some thinking about before changing thing again. I would also argue that the problem is not that chat states are saved, but that they aren't filtered from the result. Maybe I want the chat states included for reasons? Maybe you don't? How would the server know this in advance?

  4. lovetox on

    I agree with other XEPs emerging, its not so easy anymore what to store and what not, though i think in whatever solution you come up with, chatstates should be excluded per default :)

  5. Zash on

    https://hg.prosody.im/0.10/rev/93a068ef4b2c adds support for filtering out various namespaces from messages about to be archived, with chatstates as the default.

    Changes
    • owner Zash
    • tags Status-Fixed
  6. Zash on

    Changes
    • tags Milestone-0.10

New comment

Not published. Used for spam prevention and optional update notifications.