Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
poezio
poezio
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 178
    • Issues 178
    • 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
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • poezio
  • poeziopoezio
  • Issues
  • #3462

Closed
Open
Opened Feb 26, 2019 by Maxime Buquet@ppjetMaintainer

LMC replaces the whole stanza

XEP-0308 says:

It is expected that the receiver SHOULD then treat the new stanza as complete replacement for all the payloads received in the original stanza.

Poezio currently replaces the whole stanza, which makes it expect somebody sending multiple LMCs to use the last id each time, instead of the original (that it doesn't know about anymore?).

I hear some argue that this should be fixed in the XEP to specify that attributes of the original stanza should also be replaced, in the meantime, we're not exactly compliant.

What to do?

  • Raise the issue on standards@
  • Fix poezio to not replace the original stanza entirely
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
0.13
Milestone
0.13
Assign milestone
Time tracking
None
Due date
None
Reference: poezio/poezio#3462