-
Notifications
You must be signed in to change notification settings - Fork 4
MSC3911 AP5: Updating the room creation handler to recognize attaching media when restricted #96
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
6d8d0e8 to
5529009
Compare
525bda8 to
a713f08
Compare
a713f08 to
1476589
Compare
42a5d57 to
eebfb67
Compare
|
I'm not sure I like where this ended up living in the code base. Is there a better place? |
…tach restricted m.room.avatar media
eebfb67 to
c9aee37
Compare
|
Complement test failures are because the base branch does not have a current version of Synapse merged in yet. The sytest failure for Merging |
Linked Media MSC3911 AP5: Updating the room creation endpoints to allow attaching media
For https://github.com/famedly/product-management/issues/3355
Out-of-band discussion realized that passing a query argument to the room creation endpoint would be pointless, as:
m.room.avatarevent, it would do nothing appropriate(accepting room creator membership event, which should be part of the copy media system for automatic handling)m.room.avatarevent, then that is all we need to discover the media id