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

add in-room m.key.verification.request msgtype #1271

Merged
merged 5 commits into from
Nov 2, 2022

Conversation

uhoreg
Copy link
Member

@uhoreg uhoreg commented Oct 4, 2022

fixes #18

ref: matrix-org/matrix-spec-proposals#2241

Apparently, when in-room verification was added, the m.key.verification.request msgtype was forgotten.

Preview: https://pr1271--matrix-spec-previews.netlify.app

@uhoreg uhoreg requested a review from a team as a code owner October 4, 2022 21:51
@richvdh richvdh self-requested a review October 11, 2022 17:57
content/client-server-api/modules/end_to_end_encryption.md Outdated Show resolved Hide resolved
content/client-server-api/modules/end_to_end_encryption.md Outdated Show resolved Hide resolved
@@ -0,0 +1,19 @@
{
Copy link
Member

Choose a reason for hiding this comment

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

this makes an example appear under the general definition of m.room.message (https://pr1271--matrix-spec-previews.netlify.app/client-server-api/#mroommessage), which feels confusing to me.

Worse, where there ought to be an example, is just an empty "Examples" heading:

image

@@ -562,6 +565,8 @@ in this specification must be under the `m.key.verification` namespace
and any other event types must be namespaced according to the Java
package naming convention.

{{% event event="m.room.message$m.key.verification.request" %}}
Copy link
Member

Choose a reason for hiding this comment

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

this presents itself as literally m.room.message$m.key.verification.request, which is obscure to say the least:

image

It's also in conflict to the way that m.text and co are represented, though I'm not sure that format would be terribly useful either:

image

Maybe the render-event.html template thing needs to be updated to honour the title of the event definition, then we can set that to something like "m.room.message with msgtype: m.key.verification.request" ?

Copy link
Member Author

Choose a reason for hiding this comment

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

This and #1271 (comment) will be fixed by #1283

uhoreg and others added 3 commits October 12, 2022 09:52
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
@uhoreg uhoreg requested a review from richvdh October 12, 2022 20:32
Copy link
Member

@richvdh richvdh left a comment

Choose a reason for hiding this comment

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

lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

In-room m.key.verification.request message event doesn't seem to be documented
2 participants