Add OEmbed support for Animoto videos

[lritter]

As a user, I'd like to simply embed videos created and hosted by Animoto. Wordpress.com-hosted sites already support this but ".org" does not yet.

[lritter]

patch adding oembed support for animoto

[SergeyBiryukov]

For reference: ​http://make.wordpress.org/core/handbook/design-decisions/#whitelisting-oembed-providers

[johnbillion]

Animoto appears to be fairly well established.

@Iritter: could you provide some answers to the points in Sergey's link above please?

[lritter]

Replying to SergeyBiryukov:

For reference: ​http://make.wordpress.org/core/handbook/design-decisions/#whitelisting-oembed-providers

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

I don't know how to evaluate this but recent press indicates ~10m users.

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

Animoto is a simple tool for creating video from photos, music, and text. There is no equivalent tool supported right now.

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

@animoto is verified.

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

Documentation: ​http://help.animoto.com/entries/109992-oEmbed-API

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

There are a number of integration options detailed here: ​http://animoto.com/developer

How old is the service?

Animoto is 7 years old.

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

I don't know what "well-established" means but here's the article: ​https://en.wikipedia.org/wiki/Animoto

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?

Animoto wrote a plugin. I don't really know how to judge the "demand" aspect but apparently it was high enough to justify inclusion in wordpress.com.

Is the provider frequently proposed?

I don't have access to data to say either way.

[wonderboymusic]

Animoto has been around for a while, I first saw them present at a "Facebook Developers Garage" in NYC in 2008.

Followers (as with Issuu, way more than Viddler):
Facebook ~50K
Twitter 61.9K

Issuu had a couple of other core contributors chime in. If someone else agrees this should go in, it shall.

[johnbillion]

Iritter: What's the relevance of video214.com in your patch? Was this a mistake or is it also part of Animoto?

[lritter]

Replying to johnbillion:

Iritter: What's the relevance of video214.com in your patch? Was this a mistake or is it also part of Animoto?

Yes, video214.com is part of animoto. When some business users share their videos with their customers they use video214 to hide animoto branding.

[wonderboymusic]

Updated the patch to optionally allow https and www. which redirect to the animoto.com domain.

I made a video here, they are really cool: ​http://animoto.com/play/MlRRgXHhoT8gOZyHanM6TA

[wonderboymusic]

In 28790:

Add Animoto to the list of oEmbed providers. Example video: ​http://animoto.com/play/MlRRgXHhoT8gOZyHanM6TA.

Props lritter.
Fixes #28265.

[kovshenin]

Re r28790: one regex is faster than two. We can use (animoto|video214) and we also need to escape the . in .com. See 28265.2.diff​.

[SergeyBiryukov]

Replying to kovshenin:

Re r28790: one regex is faster than two.

Should we perhaps revert [28593] as well?

[kovshenin]

Replying to SergeyBiryukov: That change was for backwards compatibility reasons, though as Nacin mentioned in #28125, we've changed patterns before and will probably have a need to in the future. It'd be easier if these were keyed by unique handles, rather than regular expressions.

[SergeyBiryukov]

Well, if someone is using wp_oembed_remove_provider() to disallow YouTube embeds, they would have to make changes for playlists anyway, so I guess I'd prefer to merge those YouTube patterns too for consistency.

[SergeyBiryukov]

In 28822:

Merge two Animoto oEmbed patterns.

props kovshenin.
see #28265.

[kovshenin]

True, but at least their existing block for /watch would still be in place. I don't mind reverting r28593. Given that the array is keyed by the regex pattern, wp_oembed_remove_provider() seems pretty useless anyway :) Feel free to reopen #28125 and continue the discussion.