oEmbed provider

[candrews]

Wordpress would benefit from having an oEmbed provider. Having one would allow oEmbed consuming sites (such as those powered by laconica) to embed Wordpress content automatically.

[Viper007Bond]

Just for clarification for everyone: he's talking about a provider, not a consumer.

Example: link to one of your WordPress posts on another site and the content of the post could be read and embedded.

[mrmist]

As I said on the dev chat I reckon the provider side of this sits firmly in plugin land at the moment, simply due to the likely amount of take up weighed against any possible downsides (bloat, etc.). So it gets a -1 from me at the moment for core. Maybe wayyyy in the future, when people know about it.

[Viper007Bond]

-1 from me as well BTW. It'd almost never get used, so it's plugin territory... for now.

[Otto42]

+1 from me, but not in 2.9.

Reasoning:

• Many popular aggregator sites, such as Digg, get this information and use it correctly.
• There's enough supported in oEmbed to make it useful. A post could be represented by the "rich" type. Attachments could get the "photo", "audio", or "video" types, depending on the attachment.
• You could implement this as a new type of "feed" in WordPress quite simply. It's just an XML document with some of the content in it.

Maybe for 3.0 or 2.9.1 or something.

[Viper007Bond]

It'd be 3.0. New features don't go into minor releases.

[edwardw]

Suggesting close, but waiting for core dev feedback on this one. Two years stale - not sure what has changed over the past two years.

Some relevant links:

• ​oEmbed discovery on Codex
• ​oEmbed provider plugin (slightly outdated, 2.8.x, someone want to contact author and get him to update?)

[Viper007Bond]

I've kind-of-sorta come around on this since WP.com implemented it, but I still think it's plugin territory. Maybe the code can get rolled into Jetpack.

[nacin]

Sounds like something worthy of Jetpack/WP.com to implement. (Might be interesting for the Embed.ly plugin, too.) I doubt you'll find much traction among the core devs for this. There's a bit of a sentiment that implementing oEmbed was a bit hasty and possibly something that shouldn't have been developed for core. Thinking it's time to maybelater this, for now.