Make WordPress Core

Opened 13 years ago

Closed 11 years ago

Last modified 10 years ago

#26278 closed enhancement (fixed)

add Cloudup to core as oEmbed provider

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

Description

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:

https://cloudup.com/*

maps to:

https://cloudup.com/oembed

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

Attachments (2)

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

Download all attachments as: .zip

Change History (18)

#1 @georgestephanis
13 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 13 years ago by georgestephanis (previous) (diff)

#2 @georgestephanis
13 years ago

  • Component GeneralEmbeds
  • Keywords has-patch added
  • Severity normalminor
  • Versiontrunk

#3 @SergeyBiryukov
13 years ago

  • Type feature requestenhancement

#4 @shaunandrews
13 years ago

  • Cc shaun@… added

#5 @georgestephanis
13 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 13 years ago by georgestephanis (previous) (next) (diff)

#6 @johnbillion
13 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
13 years ago

  • Milestone Awaiting Review
  • Resolutionmaybelater
  • Status newclosed

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
13 years ago

  • Summary add Cloudup as a core oEmbed provideradd Cloudup to core as oEmbed provider

#10 @SergeyBiryukov
13 years ago

  • Version trunk3.7

#11 @markjaquith
11 years ago

  • Milestone4.3
  • Resolution maybelater
  • Status closedreopened

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.

@markjaquith
11 years ago

#12 @obenland
11 years ago

  • Owner set to markjaquith
  • Status reopenedassigned

#13 @markjaquith
11 years ago

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

#14 @markjaquith
11 years ago

  • Resolutionfixed
  • Status assignedclosed

In 33472:

Add CloudUp to our oEmbed provider whitelist.

fixes #26278

#15 @johnbillion
11 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.


10 years ago

Note: See TracTickets for help on using tickets.