Make WordPress Core

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#25265 closed enhancement (maybelater)

Add to the oEmbed whitelist

Reported by: mrgeorgegray's profile mrgeorgegray Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.6
Component: Embeds Keywords: has-patch
Focuses: Cc:


Added to wp-includes/class-oembed.php

Attachments (1)

add_mixlr_oembed_to_whitelist.diff (840 bytes) - added by mrgeorgegray 11 years ago.

Download all attachments as: .zip

Change History (5)

#1 @nacin
11 years ago

We have a certain standard for oEmbed providers in core. They must be well-established, popular, mainstream services; they must properly implement the oEmbed spec; and they must clearly be a trusted provider. Trust is more than about security — the service must also be "built to last," as if a provider ever stops supporting oEmbed, sites start to lose content they previously trusted would stay embedded permanently. Some nascent services are just too fragile to be material for core.

With regards to establishment and popularity, there are a number of "warning signs":

  • I've personally never heard of Mixlr
  • While it is for "social live audio", it didn't come up during WordPress 3.5 or 3.6, which added a lot of support for audio/video, including Spotify, Rdio, and Soundcloud via oEmbed
  • I can't find an article about it on Wikipedia
  • Even though it is a "social" platform, I almost have as many followers as @Mixlr on Twitter, and it pales in comparison to other aforementioned giants
  • It is less than a year old (at least its reincarnation)
  • The oEmbed endpoint appears undocumented:

I see you have just today added a shortcode plugin to It is best to see what kind of traction/adoption it or any other plugins may receive. (Perhaps notably, it's the only result when searching for "mixlr" in the directory.)

#2 @mrgeorgegray
11 years ago

  • Resolution set to maybelater
  • Status changed from new to closed

Thanks Nacin. We fully take on board everything you've said here. Let's see how the new plugin goes and we'll work on the other points you mentioned and perhaps review this again further down the line.

#3 @SergeyBiryukov
11 years ago

  • Milestone Awaiting Review deleted
  • Type changed from feature request to enhancement
  • Version changed from trunk to 3.6

#4 @nacin
11 years ago

I turned my comment above into a section on our nascent design decisions page:

Note: See TracTickets for help on using tickets.