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

API for deleting user & room account_data (SPEC-431) #190

Open
matrixbot opened this issue Jul 17, 2016 · 4 comments · May be fixed by matrix-org/matrix-spec-proposals#3391
Open

API for deleting user & room account_data (SPEC-431) #190

matrixbot opened this issue Jul 17, 2016 · 4 comments · May be fixed by matrix-org/matrix-spec-proposals#3391
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol p4

Comments

@matrixbot
Copy link
Member

Submitted by @​matthew:matrix.org
We seem to have deliberately avoided to specify a DELETE for account_data. Unsure why (possibly to simplify the /sync responses when it disappears?), but it's not ideal that as a result empty account_data objects start to stack up where people try to delete them

(Imported from https://matrix.org/jira/browse/SPEC-431)
@matrixbot
Copy link
Member Author

Jira watchers: @richvdh

@matrixbot
Copy link
Member Author

Yeah. We'll need synapse to support it first, of course...

-- @richvdh

@matrixbot matrixbot added the p4 label Oct 28, 2016
@matrixbot matrixbot changed the title API for deleting user & room account_data API for deleting user & room account_data (SPEC-431) Oct 31, 2016
@matrixbot matrixbot added spec-bug Something which is in the spec, but is wrong feature Suggestion for a significant extension which needs considerable consideration enhancement A suggestion for a relatively simple improvement to the protocol and removed spec-bug Something which is in the spec, but is wrong feature Suggestion for a significant extension which needs considerable consideration labels Nov 7, 2016
@turt2live turt2live added the A-Client-Server Issues affecting the CS API label Feb 6, 2019
@bmarty
Copy link

bmarty commented Sep 22, 2020

possibly to simplify the /sync responses when it disappears?

Right, this point has to be handled, maybe by adding a new section in the sync response with deleted account data...

This feature should be useful, now that we store arbitrary type in the account data, for 4S. When resetting 4S, the account data cannot be fully cleared.

@ShadowJonathan
Copy link
Contributor

Encountered this when trying to delete m.tag room account data items, it'd be very useful as it allows room/account data to be fully CRUD

@ShadowJonathan ShadowJonathan linked a pull request Sep 9, 2021 that will close this issue
Open
@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 enhancement A suggestion for a relatively simple improvement to the protocol p4
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

MSC3391: API to delete account data ShadowJonathan/matrix-doc
4 participants
@turt2live @bmarty @matrixbot @ShadowJonathan