kbondarev
commented
2 years ago Podverse developer Mitch, made this proposal on Matrix (link to thread):
mdowney:
1) Create the JP page for the episode.
2) Paste the Podverse embed code, and pass in URL param overrides for podcast title, enclosure url, episode title, episode pub date, and possibly an episode GUID, so it can render with that information immediately.
2b) We would need to disable the on-click "open episode in Podverse" behaviors while the embed is using the overridden method. Chapters and the lightning icon would also be missing.
3) Publish the JP episode page.
4) When a visitor lands on the page, the embed will first check if an episode with that enclosure url (or episode GUID) already exists in our database. If no, then the embed renders with the override params. If yes, then it ignores the override params, and loads the full parsed data we have from the RSS feed.
kiro:
Oh that sounds cool :)) Would the chapters and lightning icon be missing only when it can't find the episode in podverse database or all the time?
mdowney:
Only while it's not in our database. As long as the enclosure url and/or guid match, then it should be fully functional afterwards :) I'd go with GUID first actually, since that is more permanent
Consider using the Podverse embedded player to enable/facilitate Podcasting 2.0 features such as boosts/v4v, clips, chapters, etc.
demo: https://podverse.fm/embed/player-demo
code: https://github.com/podverse/podverse-web/pull/820/files
Value-4-value