Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-02-26 07:53:43 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Review comments

Browse source
This commit is contained in:
Daniel Wagner-Hall 2015-10-29 12:48:04 +00:00
parent b92a0f2b4d
commit cddfc110ed
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
specification/modules/third_party_invites.rst
View file

@ -22,7 +22,7 @@ and public key to the inviting homeserver.
When the invitee's homeserver receives the notification of the binding, it When the invitee's homeserver receives the notification of the binding, it
should insert an ``m.room.member`` event into the room's graph for that user, should insert an ``m.room.member`` event into the room's graph for that user,
with ``content.membership`` = ``invite``, as well as a with ``content.membership`` = ``invite``, as well as a
``content.third_party_invite`` property whichi contains proof that the invitee ``content.third_party_invite`` property which contains proof that the invitee
does indeed own that third party identifier. does indeed own that third party identifier.
Events Events
@ -94,8 +94,8 @@ For example:
H1 asks the identity server for a binding to a Matrix user ID, and has none, H1 asks the identity server for a binding to a Matrix user ID, and has none,
so issues an ``m.room.third_party_invite`` event to the room. so issues an ``m.room.third_party_invite`` event to the room.
When the third party user validates their identity, their homeserver, H3, When the third party user validates their identity, their homeserver H3
is notified, and attempts to issue an ``m.room.member`` event to participate is notified and attempts to issue an ``m.room.member`` event to participate
in the room. in the room.
H3 validates the signature given to it by the identity server. H3 validates the signature given to it by the identity server.