Opened 9 months ago
Last modified 8 months ago
#21632 reopened enhancement
Adding Imgur as an oEmbed provider
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | Embeds | Version: | |
| Severity: | normal | Keywords: | has-patch 2nd-opinion |
| Cc: |
Description
Adding imgur to the list of oEmbed providers! (wcgr rocks)
Attachments (2)
Change History (16)
- Keywords 2nd-opinion added; needs-testing removed
Similar: #11978
The thing is that there are quite a few generic image hosting providers, like imageshack, photobucket etc.
We should have a "canonical" plugin that adds support for all these addition oEmbed providers, instead of adding them to Core.
comment:3
in reply to:
↑ 2
markjaquith — 9 months ago
Replying to scribu:
The thing is that there are quite a few generic image hosting providers, like imageshack, photobucket etc.
We should have a "canonical" plugin that adds support for all these addition oEmbed providers, instead of adding them to Core.
Adding providers is really low cost for us. Knowing that they need a plugin, tracking that plugin down, and installing it, is a big hurdle for users. These "magic" embeds will work better the more that people can rely on popular embed providers to be supported without any effort on their part. I think our hurdle should be the popularity and stability of the embed provider. Imgur has been around for a while, and serves multiple petabytes a month — I think they fit the bill. And FWIW, I'd be happy to add ImageShack and Photobucket too.
comment:4
wonderboymusic — 9 months ago
Related / please add: #15734
I agree with @markjaquith. Additionally Photobucket is already supported:
http://core.trac.wordpress.org/browser/trunk/wp-includes/class-oembed.php?rev=20874#L44
- Keywords 2nd-opinion removed
- Milestone changed from Awaiting Review to 3.5
I think our hurdle should be the popularity and stability of the embed provider. Imgur has been around for a while, and serves multiple petabytes a month — I think they fit the bill.
Agreed.
I believe the correct endpoint is just http://api.imgur.com/oembed, and that the regular expression is dangerously missing a slash. (A domain like i.imgur.com.nacin would work.)
Looks like this should additionally be subdomain-agnostic.
Additionally, the endpoint requires at least a height and width of 640 (if either/both are specified) to display http://imgur.com/w7zCp, despite it being only 554 x 541. Otherwise, it provides a height/width of 90 x 90. That's pretty lame and needs more research.
Since they have a flaky endpoint, seems like this should be punted for now.
comment:10
nacin — 8 months ago
- Keywords 2nd-opinion added
- Owner set to markjaquith
- Status changed from new to assigned
comment:11
nacin — 8 months ago
- Status changed from assigned to closed
comment:12
nacin — 8 months ago
- Status changed from closed to reopened
comment:13
nacin — 8 months ago
- Keywords punt added
comment:14
nacin — 8 months ago
- Keywords punt removed
- Milestone changed from 3.5 to Future Release
Per IRC, punted until imgur obeys maxwidth and maxheight in a sane way.

Adding imgur to the list of oEmbed providers