[wp-trac] [WordPress Trac] #55278: Fix Support for embed.ly with Odysee.com (half working)

[WordPress Trac]

#55278: Fix Support for embed.ly with Odysee.com (half working)
-------------------------+------------------------------
 Reporter:  tomatodysee  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Embeds       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui
-------------------------+------------------------------

Comment (by tomatodysee):

 @peterwilsoncc answering the questions as you asked, let me know if this
 works:

 Is the service is popular enough for core developers to have heard of it
 before? Is it “mainstream?”
 Odysee has been around for 1.5 years now and evolved from lbry.tv (~2019,
 now sunset) and a LBRY Desktop application in 2016. Today, Odysee.com has
 over 32M+ monthly unique visitors and is used by prominent content
 creators, many of which have millions of youtube subscribers.

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

 Does this service have a large following on Twitter, Facebook, or other
 social media?  Is its Twitter account verified?
 Twitter account is verified and has over 55K followers:
 https://twitter.com/OdyseeTeam . This is our main social media platform,
 and on our own site, we have over 1.3M followers:
 https://odysee.com/@Odysee:8

 Is its oEmbed endpoint clearly established and properly documented?
 (Sometimes, they are just a developer’s pet project that may not be
 supported.)
 Oembed implementation can be found here: https://github.com/OdyseeTeam
 /odysee-frontend/blob/master/web/src/oEmbed.js
 We are also supported on embed.ly, and you can validate our URLs here:
 http://debug.iframely.com/?uri=https%3A%2F%2Fodysee.com%2F%40veritasium%3Af%2Fwe
 %27re-building-computers-wrong-%28for%3Af

 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 added to the allow-list?
 No, only works via paid wordpress accounts + via our embed code. Our
 iframes use cookies, and require the same-site origin flag which, as
 discussed
 above, is not secure enough based on WordPress standards.

 Does the service make an effort to build relationships with developers,
 such as through robust APIs?
 Majority of our code is open source, and we work with outside contributors
 all the time!

 How old is the service?
 1.5+ years, but LBRY has been around since 2016.

 Does it have a well-established Wikipedia article? (Seriously.)
 Right now it’s under LBRY, but we hope someone will correct that. Odysee
 is now a separate company outside of LBRY Inc (for the past ~6 months).
 https://en.wikipedia.org/wiki/LBRY

 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’s a wordpress plugin for LBRY: https://github.com/lbryio/lbrypress,
 but it didn’t get much traction. LBRY Inc is revamping it to make it
 easier to use/integrate.

 Is the provider frequently proposed?
 We get many requests from users and creators to support Odysee links on
 WordPress!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55278#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform