Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Recommend that servers don't allow clients to send tombstones for the same room #514

Open
turt2live opened this issue Jul 31, 2019 · 2 comments
Open

Recommend that servers don't allow clients to send tombstones for the same room #514

turt2live opened this issue Jul 31, 2019 · 2 comments
Labels
A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit

Comments

@turt2live
Copy link
Member

a la matrix-org/synapse#5801
@turt2live turt2live added clarification An area where the expected behaviour is understood, but the spec could do with being more explicit A-Client-Server Issues affecting the CS API labels Jul 31, 2019
@KitsuneRal
Copy link
Member

Unless my memory's failing me, there was a discussion somewhere around m.room.tombstone MSC that keeping this possible can help to re-upgrade rooms that have been incorrectly/"illegitimately" upgraded. I can't find it yet.

@turt2live
Copy link
Member Author

sorry, this is to prevent a tombstone for the room where the tombstone is sent in. Not preventing multiple tombstones from being sent.

@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@turt2live @KitsuneRal