-
-
Notifications
You must be signed in to change notification settings - Fork 140
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
client-api: Add support for authenticated media endpoints #1815
Conversation
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.
Thanks! Just two small things.
//! `/unstable/org.matrix.msc3916/` ([spec]) | ||
//! | ||
//! [spec]: https://github.com/matrix-org/matrix-spec-proposals/pull/3916 |
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.
Shouldn't we instead do the following on all these modules, like we do with (almost) all other unstable modules?
//! `/unstable/org.matrix.msc3916/` ([spec]) | |
//! | |
//! [spec]: https://github.com/matrix-org/matrix-spec-proposals/pull/3916 | |
//! `MSC3916` ([MSC]) | |
//! | |
//! [MSC]: https://github.com/matrix-org/matrix-spec-proposals/pull/3916 |
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.
Right. I think my inline code makes more sense compared to stable endpoints where we show the path segment.
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.
Meaning that here I would be for using my inline code and MSC
for the link. And try to enforce that in the future.
crates/ruma-client-api/src/authenticated_media/get_content_thumbnail.rs
Outdated
Show resolved
Hide resolved
According to MSC3916
According to MSC3916.
This does not add the federation endpoint because it seems that its format is not finalized. The MSC uses a single endpoint with a
multipart/mixed
body, to allow to include metadata with the media in the future. But there are suggestions to have separate endpoints for the metadata and the file content, or to include the metadata in the headers instead.