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

Add facade support #521

Open
jdevalk opened this issue Feb 23, 2021 · 0 comments
Open

Add facade support #521

jdevalk opened this issue Feb 23, 2021 · 0 comments

Comments

@jdevalk
Copy link

jdevalk commented Feb 23, 2021

Google recommends using facades, but doing so is relatively complicated, when the solution could be so much easier. We should add support for facades to the oEmbed specification.

What is a facade?

A facade would be a required attribute that contains a high resolution image that entices people to click. For a video, I'd think about a thumbnail of the video with a "play button" overlay, for instance, served out as a single image. On click, the full embed would be loaded. The spec should require the image to be downloaded / sideloaded into the site embedding the page. This way, there's no interaction between the site the URL was embedded from and the user until the user clicks the image, thus improving the user's privacy. This would also greatly improve site speed.

It really could be as simple as adding this as a single attribute that requires a downloadable image URL.

How does a facade differ from a thumbnail_url?

Currently, oEmbed already contains an optional thumbnail_url attribute. That attribute unfortunately is optional, and often much too low of a resolution.

This issue is the result of a thought I had when I saw this tweet by @addyosmani.

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