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

MSC4086: Event media reference counting #4086

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

AndrewRyanChama
Copy link

@AndrewRyanChama AndrewRyanChama commented Dec 23, 2023

@turt2live turt2live changed the title MSCTBD: Event media reference counting MSC4086: Event media reference counting Dec 23, 2023
@@ -0,0 +1,35 @@
# MSC0000: Reference counting media
Copy link
Member

Choose a reason for hiding this comment

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

Your MSC number is 4086. Please also wrap lines to approximately 100 characters.

@turt2live
Copy link
Member

turt2live commented Dec 23, 2023

@AndrewRyanChama please also Sign off on your changes so the MSC is elligible for acceptance later on in the process.

@turt2live turt2live marked this pull request as draft December 23, 2023 21:02
@turt2live turt2live added proposal A matrix spec change proposal s2s Server-to-Server API (federation) client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. labels Dec 23, 2023

For encrypted events, the sender must include an additional unencrypted field in the event, associated_media, which is an array of media ids.

All endpoints will follow either the existing apis, or #3916
Copy link
Member

Choose a reason for hiding this comment

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

Please use "MSCxxxx" instead of "#xxxx", and provide a link to the MSC.


The homeserver's media repository will maintain a many-many association between events and media ids. For events that are redacted, the association will be removed. For m.replaces events, the event that was replaced will have its association removed. If a media item is not associated with any event on the server, the server must delete that media item.

For newly uploaded media items, the sender must associate it with an event within a fixed amount of time (configurable by the server owner, suggested to be 1 hour), otherwise the server will delete it. In order to associate the event with media, the sender may include it in the standard url field of events such as m.image and m.sticker, or include a well formed mxc url in the message body. Any events received over federation will have their association recorded accordingly, if the media is in the homeserver's media repository.
Copy link
Member

Choose a reason for hiding this comment

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

Media can also be used as user or room avatars.

Signed-off-by: Andrew Ryan <andrewryanchama@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff 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 s2s Server-to-Server API (federation)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants