oEmbed: Add VideoPress as a provider

[kraftbj]

VideoPress now has permalinks with oEmbed support, based on the WP.com oEmbed API (already supported). We already support WordPress.tv, which is, at this point, a "wrapped" for VideoPress.

Per the core list:

• Is the service is popular enough for core developers to have heard of it before? Is it “mainstream?”

As WP-centric video hosting, I think it is popular without our ecosystem.

• If similar services are already supported, how does this service compare in terms of size, features, and backing?

The revamp brought it on par with player features in FB, Vimeo. Since VideoPress is focused as WordPress video hosting, there is not a separate "portal".

• Does this service have a large following on Twitter, Facebook, or other social media? Is its Twitter account verified?

As part of the offering from WordPress.com, I'd say that WP.com's following is sufficient.

• Is its oEmbed endpoint clearly established and properly documented? (Sometimes, they are just a developer’s pet project that may not be supported.)

It is part of the WP.com API. Details, including VideoPress reference: ​https://developer.wordpress.com/docs/oembed-provider-api/

• Does the service make an effort to build relationships with developers, such as through robust APIs?

While being an Automattic property merits zero special consideration, being so close to Core dev, all ears!

• How old is the service?

First iteration: 2009.
Revamp that added oEmbed/permalinks: July 2015

• Does it have a well-established Wikipedia article? (Seriously.)

No. It is mentioned under ​https://en.wikipedia.org/wiki/Automattic, but does not have anything more as far as I know.

• Has anyone written a WordPress plugin that leverages the service in some way, whether adding it as an oEmbed provider, creating a shortcode, or leveraging other APIs of the service? Do these plugins have any noticeable adoption or traction that would indicate usage and demand?

Jetpack has a VideoPress module that enables many features natively for self-hosted sites, which is slated for near-future improvements. It creates a shortcode and adds VideoPress as an oEmbed provider.

• Is the provider frequently proposed?

Unknown.

Additionally, I'll note that the lack of a native VideoPress oEmbed on Core caused some confusion for the 4.3 release video (first since the enhancement). While WordPress.tv URLs work in Core, folks attempting to paste in the share URL from the player (videopress) found it unsuccessful.

[kraftbj]

Adds VP as a provider.

[kraftbj]

Some notes about the patch:

1. Spacing needs to be adjusted if/when committed. Opted for the minimal functional change for the patch for the sake of conversation. Can update upon request :)

2. The WP.com oEmbed API requires a for parameter for the requesting site. I've opted to set this as a variable before the array for future use, if others in the future need something like this.

3. I've opted to add the query string directly onto the URL as it is done for other providers higher up in the array.

[johnbillion]

Thanks for the patch. Moving to the next major release milestone for consideration as we always do.

VideoPress crossed my mind once before, but upon looking into it it appears that VideoPress only works with either a) WordPress.com, or b) Jetpack. So, what's the use case for supporting VideoPress in core?

Also the for query variable probably needs to be urlencode()-d rather than escaped.

[johnbillion]

Replying to johnbillion:

So, what's the use case for supporting VideoPress in core?

Answering my own question, I hadn't realised that VideoPress videos had shareable URLs. So that's the use-case.

[kraftbj]

urlencode is better :) Thanks John!

[kraftbj]

Replying to johnbillion:

Also the for query variable probably needs to be urlencode()-d rather than escaped.

You're right. Updated to urlencode. esc_url is for display, not this.

[azaozz]

34031.2.diff looks good. Wondering if we should pass just the domain, but either seems good.

[johnbillion]

In 34785:

Add VideoPress as a trusted oEmbed provider.

Fixes #34031
Props kraftbj