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

[WordPress Trac]

#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                                           |
-------------------------------------------------+-------------------------
Changes (by SirLouen):

 * keywords:  dev-feedback has-test-info has-patch needs-user-docs => has-
     test-info has-patch needs-user-docs


Comment:

 Replying to [comment:46 brhodes]:
 > I still don't know the fate of this ticket?
 >
 > We are just asking to get https://app.screencast.com on the allow list
 to use our oEmbed implementation for media. This site is a replacement for
 https://www.screencast.com which was already on the WordPress allow list.
 All our users from the old site have been migrated over to the new one.
 >
 > It looks like the patch was made and tested to get this to happen. So
 why now the desire to bury it?

 It's not a desire to bury it. It's just an opportunity to reevaluate
 whether it is time to bury it or not. Generally, when these "events"
 happen (changing URL like in this case), many things have to be
 considered. There is a backwards compatibility policy that somewhat
 inhibits removing things that work. But since screencast will be
 deprecated in favour of `app.screencast`, that doesn't really exist in WP
 yet. As I said, it's a big opportunity to reevaluate and decide if
 screencast will be merged into a newer version, or if it's time to fully
 wipe this.

 Services with oEmbed whitelisting change a lot over the time from what
 they were originally, and the only thing that "saves them" is the
 backwards compatibility policy I was talking about before. But still, as I
 said @dustintechsmith if you want this to progress, this is something to
 be discussed openly.

 The fact that this has a patch, that was brought by me in my last `bug-
 scrub` and has been code-reviewed, still is not enough to make a pass.
 Still, Joe, was willing to speak with the managers of Screencast to see if
 they could add some accessibility features to the resulting oEmbed. Maybe
 if they are willing to collaborate, this could pass anytime soon.

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