How to oembed a player for Simplecast audio

AI-generated summary

The discussion revolves around issues with embedding Simplecast audio players using oembed in Discourse. jtbayly initially reports that Simplecast links don’t embed properly despite supporting oembed. zogstrip notes that Simplecast’s OpenGraph data incorrectly uses type=website, which prevents embedding, but mentions that iframely works because it uses Twitter Card data. nbianca addresses the issue by implementing a fix, including a pull request to support Twitter Cards and oembed for Simplecast. Seth_Godin later reports that the embedding stopped working again, prompting further investigation. codinghorror clarifies that the correct link format is https://tgd.simplecast.com/episodes/..., and ahd2109 confirms the issue persists. nbianca identifies that Simplecast’s oembed endpoint fails for certain URLs, leading to a bug in the onebox logic, which she fixes. The issue is resolved, and the community thanks her for the fix codinghorror.

I’m really confused why this isn’t embedding an audio player:

https://simplecast.com/s/7fe152f4

They support oembed, as can be seen here: https://oembed.com (search on the page for simplecast).

My first thought is that I need to whitelist it, and it’s just not whitelisted here. However, I turned on “enable inline onebox on all domains” and that didn’t help on my site. Then I tried whitelisting simplecast.com. That didn’t help either. Any thoughts?

edited to add: appears to work properly on iframely

Their OpenGraph data has a type = website …

Ok… interesting. So, what should it be? I might be able to get them to fix it.

And why does it appear to work properly in iframely?

Because they use the data from the Twitter Card.

I think we should properly support Twitter Cards with a type of player.

@nbianca, can you add that to your list? We should update our WhitelistedGenericOnebox to properly detect embeds in Twitter Cards

I let them know about the issue. I guess it’s a race to see who can fix it first. :wink:

:slight_smile:

https://github.com/discourse/onebox/pull/390/files

Looking forward to trying this!

Does this work?

https://simplecast.com/s/7fe152f4

Should the above work @nbianca?

Simplecast are not providing twitter cards info anymore, so I had to implement an oembed onebox for them.

https://github.com/discourse/onebox/pull/403

FWIW, Simplecast recently went through a big change to a new 2.0 codebase. Lots changed. I did tell them recently that their stuff isn’t auto-embedding like they claim.

They say “Use this link to share via social media. It will automatically embed a player in WordPress, Medium, and many other popular sites.” with a link such as this:
https://tgd.simplecast.com/episodes/dan-blackman-and-robyn-kanner-the-power-7fe152f4

It doesn’t work on Wordpress.com or self-hosted Wordpress. Let’s test it again now here on Meta:

Edit: Looks like it’s working!

Crossposting here from a later thread about this issue

It seems as though after working great, onebox isn’t working again on Simplecast. Any thoughts? Thanks.

Let’s see if the old link posted above still oneboxes

https://tgd.simplecast.com/episodes/dan-blackman-and-robyn-kanner-the-power-7fe152f4

Yes that link works fine @Seth_Godin

The link is substantially different from the one you posted which is

https://simplecast.com/s/19cdf3ea

compare with

https://tgd.simplecast.com/episodes/dan-blackman-and-robyn-kanner-the-power-7fe152f4

did some more digging. Here’s how Simplecast now offers people a way to share a link:

As you can see, the old model isn’t supported any more.

Not sure if this is on the onebox roadmap, but it’s clearly a change on their part. Thanks.

EDIT! Wait, this might do the trick… I add the word ‘embed’ to the url and get this:

Maybe we need to widen the URL patterns we look for here from this domain @nbianca?

Jumping in here! I migrated to the “new” simplecast in order to get the updated URL, like the one you posted from TGD, @codinghorror, but it still appears as a link rather than onebox

checking on this @codinghorror!!

Sure @nbianca can take a look and see if the URL patterns can be broadened for better compatibility.

thank you @nbianca! lmk how i can help