[wp-trac] [WordPress Trac] #53448: Add Pinterest as a whitelisted oEmbed provider

[WordPress Trac]

#53448: Add Pinterest as a whitelisted oEmbed provider
-------------------------+-------------------------
 Reporter:  pento        |      Owner:  pento
     Type:  enhancement  |     Status:  assigned
 Priority:  normal       |  Milestone:  5.9
Component:  Embeds       |    Version:
 Severity:  normal       |   Keywords:  needs-patch
  Focuses:               |
-------------------------+-------------------------
 I'd like to propose that we add Pinterest as a
 [https://make.wordpress.org/core/handbook/contribute/design-decisions
 /#whitelisting-oembed-providers trusted oEmbed provider].

 They provide [https://www.pinterest.com/oembed.json a single oembed
 endpoint], which handles URLs of pins, boards, and profiles.

 To answer questions listed in the trusted oEmbed provider handbook page:

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

 Yes, definitely.

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

 I don't believe we currently have a favourite-ing service on the list of
 trusted providers.

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

 [https://twitter.com/Pinterest Yep].

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

 I'm not aware of any documentation for the endpoint.

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

 Interestingly, while they do offer auto-discovery, WordPress doesn't
 support it. The [https://oembed.com/#section4 oEmbed spec] allows auto-
 discovery to be defined in `<link>` tags, ''or'' in `Link` HTTP headers:
 WordPress checks for the tags, but not the headers.

 There's potentially an argument to be made for adding support for auto-
 discovery through headers, but since this is the first service I've ever
 seen that uses it, I would see that as a fairly low priority.

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

 The provide a handful of relevant APIs and
 [https://developers.pinterest.com/docs/widgets/getting-started/
 documentation].

 > How old is the service?

 11 years old.

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

 [https://en.wikipedia.org/wiki/Pinterest 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?

 There are [https://wordpress.org/plugins/search/pinterest/ a bunch of
 relevant plugins], though it's usually bundled in with other social
 network support. Notably, Jetpack includes a Pinterest block that sees a
 decent amount of usage.

 > Is the provider frequently proposed?

 This is the first proposal that I'm aware of.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53448>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform