Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
biboumi
biboumi
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 88
    • Issues 88
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 7
    • Merge Requests 7
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • louiz’
  • biboumibiboumi
  • Issues
  • #3305

Closed
Open
Opened Oct 17, 2017 by ge0rg@ge0rg

Force-join not properly implemented

When a client got desynchronized and joins a MUC, it sends a <presence><x/></p> stanza. The MUC service (biboumi in this case) should react by properly syncing the client, even if it is still listed as a participant.

Background: https://github.com/xsf/xeps/pull/499

Currently, the rejoining client will only receive partial presence updates, and won't be able to list all channel participants.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
8.0
Milestone
8.0
Assign milestone
Time tracking
None
Due date
None
Reference: louiz/biboumi#3305