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.

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

MSC4004: unified view of identity service #4004

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

guimard
Copy link

@guimard guimard commented Apr 26, 2023

Rendered

Centralized chat platforms are able to automatically detect which entries of
the phone address book are known by the platform, then automatically propose
those names when user clicks on "new discussion".

The Matrix-Identity-Service has already a secured mechanism able to be used
for this (lookup). However, the identity service is only able to answer
with data it knows (ie submitted lookups).

This MR proposes a mechanism to give an unified view of the identity service

Signed-off-by: Xavier Guimard [email protected]

@guimard guimard force-pushed the unified-identity-service branch from a9910e1 to 96a4ea6 Compare April 26, 2023 07:34
@guimard guimard changed the title Draft: MSC-4003: unified view of identity service Draft: MSC-4004: unified view of identity service Apr 26, 2023
@uhoreg uhoreg marked this pull request as draft April 26, 2023 13:23
@uhoreg uhoreg changed the title Draft: MSC-4004: unified view of identity service MSC-4004: unified view of identity service Apr 26, 2023
@uhoreg uhoreg added proposal A matrix spec change proposal identity service 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. labels Apr 26, 2023
@turt2live turt2live changed the title MSC-4004: unified view of identity service MSC4004: unified view of identity service May 2, 2023
@turt2live
Copy link
Member

@guimard please note that in order for us to accept this (a much later step in the spec process), we'll need Sign Off on the changes.

@guimard guimard force-pushed the unified-identity-service branch from 1fb24e9 to fa52ecf Compare May 11, 2023 02:33
@guimard
Copy link
Author

guimard commented May 11, 2023

@guimard please note that in order for us to accept this (a much later step in the spec process), we'll need Sign Off on the changes.

Hi @turt2live, I just added the "signed-off". Thanks !


## Potential issues

To avoid conversation hijacking, only trusted server should be allowed to push
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How are these trusted servers going to be determined? How are pushing servers supposed to know if they are trusted?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @MTRNord,
there are already some "trusted servers" parameters in Matrix-Synapse, I don't know if the way to trust servers should be part of this MSC, shouldn't it ?

@guimard guimard marked this pull request as ready for review November 28, 2023 11:19
@guimard guimard force-pushed the unified-identity-service branch from fa52ecf to 0dc9633 Compare December 6, 2023 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
identity service 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. proposal A matrix spec change proposal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants