Conversation
There was a problem hiding this comment.
Implementation requirements:
- Server
- Appservice
There was a problem hiding this comment.
element-hq/synapse#19458 exists now
matrix-org/matrix-hookshot#1217 exists nower
element-hq/matrix-bot-sdk#85 exists even more nower
Co-authored-by: Patrick Cloke <[email protected]>
…c-proposals into hs/as-url-previews
| the `og:image` specified in OpenGraph data be in MXC format. The appservice MUST do this upload step and respond | ||
| to the homeserver with a MXC URI. | ||
|
|
||
| ## Potential issues |
There was a problem hiding this comment.
A downside of this is also that it requires admins to setup a URL provider as an appservice, instead of something more self-serve / similar to Slack plugins that allow specific preview providers.
That's also true today, but maybe worth considering.
There was a problem hiding this comment.
Yup, it's certainly true. There has been the idea floated about that we just do these previews on the client in the future, but that limits you to native clients and it doesn't work if you have specific rules in place about who can access what.
I think the expectation would be that you'd either have an appservice hanging around (a lot of folks run a hookshot on the side these days 😇 ) or your provider would allow you to do trivial steps to install one (ESS provides most of this today).
I think if we were a closed protocol and there was a whole app store infrastructure in front of you we wouldn't even bother with this design, but thems the limitations.
Rendered
Conflict of Interest declaration: I am employed by Element. This MSC was written as part of my work on improving integrations in Element with other apps.