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

Mechanism to communicate 3PID binding updates or deletions to homeservers #3808

Closed
babolivier opened this issue Jun 20, 2018 · 3 comments
Closed

Mechanism to communicate 3PID binding updates or deletions to homeservers #3808

babolivier opened this issue Jun 20, 2018 · 3 comments
Labels
kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. obsolete A proposal which has been overtaken by other proposals proposal A matrix spec change proposal

Comments

@babolivier
Copy link
Contributor

Documentation: https://docs.google.com/document/d/1LPHBfJQ6x5iOkm2_ZYPNHNjyAzJ4hWNdOGcPGpnEb14
@babolivier babolivier added the proposal A matrix spec change proposal label Jun 20, 2018
@babolivier babolivier changed the title Mechanisms to communicate binding updates or deletions between homeservers and identity servers Mechanism to communicate binding updates or deletions to homeservers Jun 20, 2018
@babolivier babolivier changed the title Mechanism to communicate binding updates or deletions to homeservers Mechanism to communicate 3PID binding updates or deletions to homeservers Jun 20, 2018
@babolivier
Copy link
Contributor Author

babolivier commented Jun 20, 2018 •
edited
Loading

As @maxidor pointed out to me in PM, part of this proposal shoud be reworked to be compliant with spec HS 3.5 which states that bindings on ISs and bindings on HSs are independant, therefore we shouldn't consider changes regarding one to have direct consequences upon the other.

@uhoreg
Copy link
Member

uhoreg commented Feb 19, 2020

@babolivier Is this still needed? It seems like it's going in the opposite direction from the privacy work that was done last year.

@turt2live turt2live added the kind:feature MSC for not-core and not-maintenance stuff label Apr 21, 2020
@turt2live turt2live added the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Jun 8, 2021
@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
@ara4n ara4n transferred this issue from matrix-org/matrix-spec May 9, 2022
@babolivier
Copy link
Contributor Author

Looks like this has already been covered by the unbinding work that happened a while ago.

@turt2live turt2live added the obsolete A proposal which has been overtaken by other proposals label May 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. obsolete A proposal which has been overtaken by other proposals proposal A matrix spec change proposal
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@uhoreg @turt2live @anoadragon453 @richvdh @babolivier