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

MSC3551: Extensible Events - Files #3551

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

Conversation

turt2live
Copy link
Member

@turt2live turt2live commented Dec 7, 2021

@turt2live turt2live changed the title Extensible Events - Files MSC3551: Extensible Events - Files Dec 7, 2021
@turt2live turt2live added kind:core MSC which is critical to the protocol's success 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 proposal-in-review labels Dec 7, 2021
@turt2live turt2live marked this pull request as ready for review December 7, 2021 22:50
"hashes": {
"sha256": "fdSLu/YkRx3Wyh3KQabP3rd6+SFiKg5lsJZQHtkSAYA"
},
"v": "v2"
Copy link
Member

Choose a reason for hiding this comment

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

The v field name is a bit weird here, since it's specific to the encryption stuff. Might be nicer to have something like encrypted_version and then use the presence and value of that field to determine if the file is encrypted (and if it's supported) rather than using the presence of key. Alternatively, the encryption parts could be nested in an another object.

Copy link
Member Author

Choose a reason for hiding this comment

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

another object sounds appealing tbh: m.encrypted for all the encrypted things.

will consider the alternatives

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:core MSC which is critical to the protocol's success 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
Status: Scheduled - v1.10
Development

Successfully merging this pull request may close these issues.

3 participants