Make WordPress Core

Opened 5 years ago

Closed 3 years ago

Last modified 20 months ago

#26278 closed enhancement (fixed)

add Cloudup to core as oEmbed provider

Reported by: tootallnate Owned by: markjaquith
Milestone: 4.3 Priority: normal
Severity: minor Version: 3.7
Component: Embeds Keywords: has-patch
Focuses: Cc:


I see that there is a handful of out-of-the-box supported oEmbed providers, and now that Cloudup is a property of Automattic, it seemed like a cool idea to me to make Cloudup an out-of-the-box provider in WP core as well.

The oEmbed mapping is very simple:


maps to:


Let me know if anything else is needed to fulfill this request. Cheers!

Attachments (2)

26278.diff (807 bytes) - added by georgestephanis 5 years ago.
26278.2.diff (777 bytes) - added by markjaquith 3 years ago.

Download all attachments as: .zip

Change History (18)

#1 @georgestephanis
5 years ago

I believe that requirements to be a core oEmbed provider are basically ... support oEmbed, have a decent userbase, and be cool. I think Cloudup covers all three, Automattic's irrelevant to the matter at hand.

I'll shoot off a patch shortly.

Last edited 5 years ago by georgestephanis (previous) (diff)

#2 @georgestephanis
5 years ago

  • Component changed from General to Embeds
  • Keywords has-patch added
  • Severity changed from normal to minor
  • Version set to trunk

#3 @SergeyBiryukov
5 years ago

  • Type changed from feature request to enhancement

#4 @shaunandrews
5 years ago

  • Cc shaun@… added

#5 @georgestephanis
5 years ago

Shaun just mentioned something to me a few minutes ago -- Cloudup isn't actually open to general signups yet (something easy to forget when you're used to using it all the time).

Best plan would be ... what, wait for it to open to public signups, then roll it in?

Version 1, edited 5 years ago by georgestephanis (previous) (next) (diff)

#6 @johnbillion
5 years ago

Cloudup should not get special treatment just because it's an Automattic property. It's still a new service.

Replying to georgestephanis:

I believe that requirements to be a core oEmbed provider are basically ... support oEmbed, have a decent userbase, and be cool.

There's actually a considerable list of checkpoints when considering whitelisting a new oEmbed provider.

Cloudup is a very nifty service but it doesn't tick many of the points on that list.

#7 @dd32
5 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to maybelater
  • Status changed from new to closed

When/if CloudUp becomes popular and hits all the requirements in the above document, we can re-consider this. Until then, this is a wontfix/maybelater, I'd suggest looking into adding a plugin instead until then.

#9 @ramoonus
5 years ago

  • Summary changed from add Cloudup as a core oEmbed provider to add Cloudup to core as oEmbed provider

#10 @SergeyBiryukov
5 years ago

  • Version changed from trunk to 3.7

#11 @markjaquith
3 years ago

  • Milestone set to 4.3
  • Resolution maybelater deleted
  • Status changed from closed to reopened

CloudUp is open to public signups now. It’s still here, and more of the requirements are met than were back in 2013.

I'm re-opening this for consideration.

3 years ago

#12 @obenland
3 years ago

  • Owner set to markjaquith
  • Status changed from reopened to assigned

#13 @markjaquith
3 years ago

@helen said she's +1 (in person).

#14 @markjaquith
3 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

In 33472:

Add CloudUp to our oEmbed provider whitelist.

fixes #26278

#15 @johnbillion
3 years ago

In 34459:

Add an entry for Cloudup to the list of oEmbed providers.

See #26278

This ticket was mentioned in Slack in #slackhelp by macmanx. View the logs.

20 months ago

Note: See TracTickets for help on using tickets.