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

WordPress Trac noreply at wordpress.org
Fri Jun 20 14:15:12 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 paulstanos):

 Hi Peter. My name is Paul Stanos, lead developer of Screencast Classic. I
 wanted to jump in here and give some additional context on the history of
 these URLs and why some my not be resolving anymore.

 > thumb.screencast.com no longer resolves

 That's true, though to my knowledge we never provided those URLs for users
 of Classic to copy-paste. The `oembed` API may have returned them, but
 it's not intended for direct usage by users.

 From your post, it sounds like these are cached URLs pulled from the
 `oembed` endpoint?

 > legacy URLs of embedded content on content.screencast.com no longer work

 Back in 2019, we stopped generating embed codes with
 `content.screencast.com` links. Instead, we use the `/embed` style URL on
 the `www.screencast.com` domain, like the one you provided.

 When we shutdown Classic in 2025, most direct `content.screencast.com`
 URLs stopped working. We were able to maintain links to images, but not
 videos due to technical limitations of the new storage backend.

 I understand that creating dead links isn't ideal, but hopefully this
 added context shows that we did take steps to minimize this, and gave a
 long runway for old links to get used less and less over the years.

 > This has broken all previous embeds.

 When we migrated content from Classic into the new system, we created
 redirects for `/embed` links where possible. However, the URLs that are
 cached may no longer be valid for other reasons.

 Content that was deleted, moved, or made private are some of the common
 reasons that these URLs don't work anymore. The example link you gave is a
 result of that content having been moved to a different folder, making the
 URL invalid. This is not a result of the migration, but of the user making
 changes on their end.

 Given what I recall about our implementation and testing, there should be
 `/embed` URLs that are still valid and will properly redirect to their
 location in new Screencast.

 ----

 Hopefully this gives a greater understanding of the decisions made and our
 efforts to maintain links working where reasonable.

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


More information about the wp-trac mailing list