[wp-trac] [WordPress Trac] #61941: Adding app.screencast.com as an oEmbed provider

WordPress Trac noreply at wordpress.org
Thu Jun 12 21:03:11 UTC 2025


#61941: Adding app.screencast.com as an oEmbed provider
-------------------------------------------------+-------------------------
 Reporter:  brhodes                              |       Owner:  joedolson
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Embeds                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-test-info has-patch needs-user-  |     Focuses:
  docs                                           |
-------------------------------------------------+-------------------------

Comment (by SirLouen):

 Replying to [comment:53 joedolson]:
 > Yes; those worked, but the original submitted URLs didn't. I want to
 know whether that's intentional. It's not a good implementation if there's
 inconsistency in how the endpoint resources behave, so I want to explore
 further *why* specific resources aren't working.

 This is, probably, the moment when Peter discovered why public testing
 artifacts were useful for providing support for an oEmbed without having
 to doing all the registering process through their enterprise system or
 without having to deal with the support representatives.

 Just for QA purposes, I think I'm going to take some time this weekend and
 do a quick audit for the current oEmbeds and deliver this for the next
 `dev-chat`. As we commented, this is nothing very fascinating, but I think
 that something public, easily accessible, should be like the minimum
 essential for an oEmbed support, then the rest of the categories.

 [[Image(https://i.imgur.com/D7cBNf2.png)]]

 Tomorrow they change whatever thing in their embedding code, and we have
 here a number of guys creating a report with the problem and for anyone to
 develop, test and review the patch, having to do a whole research
 including having to register on a service you are not even going to use,
 to find out what is going on.

 And this is still as easy as creating a simple plugin and listing in the
 repo. Anyway, as you said, until 6.9 there are still months to go.

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


More information about the wp-trac mailing list