-
Notifications
You must be signed in to change notification settings - Fork 4
MSC3911 AP3: Update methods for sending events to allow attaching media #93
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
Conversation
nico-famedly
left a comment
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.
Looks good in general, but I think we need to figure out the multiple events case as well as the potential persistence race.
nico-famedly
left a comment
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.
Looks good to me in general, but could use some minor cleanups :)
cd18754 to
a80fe44
Compare
|
Had a As such, it has been reverted |
b33bbda to
227e429
Compare
6d8d0e8 to
5529009
Compare
https://github.com/famedly/product-management/issues/3353
Allow two endpoints:
PUT /_matrix/client/v3/rooms/{roomId}/state/{eventType}/{stateKey}PUT /_matrix/client/v3/rooms/{roomId}/send/{eventType}/{txnId}To have query parameter
org.matrix.msc3911.attach_media(attach_mediaonce stabilized) that accepts a list ofmxcurls(both with and without themxc://scheme)The
mxcreferences should have been uploaded previously.By passing these
mxcreferences to these endpoints, an association between the event being created and the piece(s) of media will be formed. Restricting the media to be viewable based on event visibility criteria is a future work.