Development
W1siziisijiwmtmvmdqvmjyvmtqvmdevmdevndyvzgv2lmpwzyjdxq-03de3c5c

Hendrik Mans - January 27, 2013

Dear Vine/Twitter et al, please support oEmbed, and support it properly.

This is a rallying cry for companies like Vine/Twitter (and similar) to please, please continue supporting oEmbed, an “open format designed to allow embedding content from a website into another page” (Wikipedia).

This site uses oEmbed to enable users to embed rich media content (like video, or tweets) from external sites simply by pasting the URL. In some cases, this isn’t exactly easy. Here’s a couple of things I’ve been struggling with lately:

  • Not every media provider supports oEmbed. (Some providers don’t even support embedding. This is the case for Vine right now, for example, but I guess it’s because they want people to embed tweets containing vines instead.) There’s a commercial oEmbed aggregator called Embedly that works around this limitation in some ways, but we don’t have an open format just to be forced to use a commercial service to use it properly, right?
  • Some companies appear to get oEmbed wrong. Twitter’s V1 API has a great oEmbed endpoint; however, this API version is deprecated and is said to be shut down some time in 2013, with version v1.1 replacing it. v1.1 also has an oEmbed endpoint, but for some reason I can’t quite fathom, it requires OAuth authentication. Derp.

I’m creating this post hoping that it will get indexed by Google and, some beautiful day, find its way to the right people.

W1siziisijiwmtmvmdkvmjuvmtuvmzgvntevmte2l2htyw5zx2j1zxjzdguyx3nxdwfyzs5qcgcixsxbinailcj0ahvtyiisijeymhgxmjajil1d-145faed7

Developer dude from Hamburg, Germany. Among other things, runs sloblog.io. Not good with descriptions. Don’t follow me on Twitter. ★

Loading comments...

Please sign in to post a comment.