-
Notifications
You must be signed in to change notification settings - Fork 385
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
base: main
Are you sure you want to change the base?
Conversation
a9910e1
to
96a4ea6
Compare
1fb24e9
to
fa52ecf
Compare
Hi @turt2live, I just added the "signed-off". Thanks ! |
|
||
## Potential issues | ||
|
||
To avoid conversation hijacking, only trusted server should be allowed to push |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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 ?
Signed-off-by: Xavier Guimard <[email protected]>
fa52ecf
to
0dc9633
Compare
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]