WordPress.org

Make WordPress Core

Opened 7 weeks ago

Last modified 7 weeks ago

#43962 new enhancement

Ziggeo oEmbed Whitelisting

Reported by: oliverfriedmann Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Embeds Keywords: reporter-feedback
Focuses: Cc:

Description

Disclaimer: Not sure this is the right place, but we were forwarded from Developer Support <developers@…> to post this here.

As per:

https://make.wordpress.org/core/handbook/contribute/design-decisions/#whitelisting-oembed-providers

We would like to apply to be considered from oEmbed whitelisting on Wikipedia.

As per the different criteria you list there:

  • be well-established, popular, and mainstream services

We have been around since 2012 and won a variety of awards for being the best API for video recording and playback.

  • properly and fully implement the oEmbed specification,

We do and are being recognized as oEmbed provider by Tumblr, Embedly, Facebook, LinkedIn and Twitter.

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

We have participated as sponsors in all major hackathons (including TC Disrupt) and have established our own yearly hackathon videohackday.com for the past four years now; we are the go to place for engineers and companies alike for all video recording and playback needs.

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

We have around 4.5k followers on Twitter, much more than most other SaaS companies. The account is not verified because Twitter vertification has been stopped.

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

Yes. See https://ziggeo.com/docs

  • Does the oEmbed endpoint work with WordPress’ oEmbed auto-discovery? If not, could it be made to work with additional HTML tags or attributes being whitelisted?

It should work with auto-discovery.

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

Our main business is an API.

  • How old is the service?

6 years

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

Yes.

  • 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?

Yes. Ziggeo has an official plugin on WP.

Thank you for your consideration.

Change History (2)

#1 @johnbillion
7 weeks ago

  • Keywords reporter-feedback added
  • Summary changed from oEmbed Whitelisting to Ziggeo oEmbed Whitelisting

Thanks for the ticket @oliverfriedmann .

You mention that Ziggeo "should work with auto-discovery". Can you check and confirm if this is the case? Of so, there's no need for Ziggeo to be whitelisted because WordPress uses oEmbed auto discovery for embedding URLs from services that aren't in the whitelist.

#2 @oliverfriedmann
7 weeks ago

Thanks @johnbillion.

Yes, but is severely limited in functionality this way. So a more "regular" whitelisted embed would be preferable.

Note: See TracTickets for help on using tickets.