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

Impact of unauthenticated media ban (MSC3916) #87

Open
sebix opened this issue Feb 6, 2025 · 0 comments
Open

Impact of unauthenticated media ban (MSC3916) #87

sebix opened this issue Feb 6, 2025 · 0 comments

Comments

@sebix
Copy link

sebix commented Feb 6, 2025

Matrix and Synapse are sunsetting the unauthenticated access to media files

https://matrix.org/docs/spec-guides/authed-media-servers/
https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/
element-hq/synapse#17950

What is the impact this will have on stickers and the Maunium sticker picker?

element-hq/synapse#17950 (comment)

that's the point, since this change all media is require auth, so custom stickers in maunium that is based off msc1951, don't load, well you can send them (maybe), but you won't see any preview of what sticker are you sending, and it is literally the only way to use custom stickers in element.

Would that mean, that all stickers that are hosted on Matrix-Servers will then no longer work? (all the ones in packs/)
Can we prevent that by self-hosting the stickers?
What changes are required in the Sticker Picker code itself, e.g. the API endpoints:

const makeThumbnailURL = mxc => `${HOMESERVER_URL}/_matrix/media/v3/thumbnail/${mxc.slice(6)}?height=128&width=128&method=scale`

@sebix sebix changed the title Impact of unauthenticated media ban Impact of unauthenticated media ban (MSC3916) Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant