Improve oEmbed support for Photobucket

[johnbillion]

Previously: #28379

Photobucket should be removed as an oEmbed provider. Finding an oEmbeddable URL for an image on Photobucket is all but impossible, and both the site and its oEmbed endpoint perform redirects on redirects on redirects.

If anyone objects, speak now or forever hold your peace.

[pento]

I'm more inclined to fix it than remove it. It's still pretty popular on WP.com, with ~500k embeds per day.

[atomicjack]

Out of interest, if this were to be removed, what happens to content already included the Photobucket oEmbed URLs? Do their images break?

[johnbillion]

When photobucket.com/oembed?url=http://i123.photobucket.com[...] is requested, it redirects to api.photobucket.com which in turn redirects to api123.photobucket.com.

We could cut out one of the redirects by switching the oEmbed endpoint to api.photobucket.com, which it clearly should be anyway.

Sending the main photo page's URL to the oEmbed endpoint results in a 404. You need to use the 'Direct' URL from the 'Share Links' section on the page. @pento / @jkudish Does the partnerships team at WP.com have a contact at Photobucket? It'd be good if these URLs were embeddable. I suspect that WP.com's implementation supports the main photo page URL.

[Viper007Bond]

+1 to fix. As annoying as this is, it's still a widely used service that we should work to support.

[johnbillion]

In 34526:

Update the oEmbed endpoint URL for Photobucket.

Fixes #33783