#680 MUC status code 100 is sent to all participants

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

    Please provide a snippet of the part of the specification which we violate if possible: If the user is entering a room that is non-anonymous (i.e., which informs all occupants of each occupant's full JID as shown above), the service MUST warn the user by including a status code of "100" in the initial presence that the room sends to the new occupant Please provide a link to the specification: http://xmpp.org/extensions/xep-0045.html#enter-nonanon In trunk as of 6bf4c227c8f3, the status code is attached to the "base <x>" argument passed to the room:publicise_occupant_status method, which is then broadcasted to all participants. It sends different <x> to the occupant itself, but exposes no way to include specific status codes there.

  2. Zash on

    Changes
    • tags Milestone-0.10
  3. Zash on

    Err, I mean trunk.

    Changes
    • tags Milestone-0.11
  4. MattJ on

    Changes
    • tags Status-Accepted
  5. Nikolay Amiantov on

    This seems to generate spam in non-anonymous MUC rooms; see https://dev.gajim.org/gajim/gajim/issues/7052.

  6. Zash on

    Hopefully fixed in https://hg.prosody.im/trunk/rev/ce461a67d2cc I can't say that I understand what the code changed there does, so please test the fix.

    Changes
    • owner Zash
    • tags Status-Fixed

New comment

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