Update the Podcast screen UX for podcasts with the "serial" RSS tag

@evoterra provided a list of feature improvements for listening to podcasts that have the serial RSS tag. Most podcasts with the serial tag fit the fiction, True Crime, or storytelling genres, and our default sorting of reverse chronological order is not the type of sorting and grouping that most serial podcast listeners would want by default.

I'm copy and pasting his recommendations here, and will try to keep all the work for this in one ticket.

[ ] Respect the >serial< - Fiction podcasts (and True Crime, docuseries, educational, and other podcasts) often are designed to be listened to from start to finish, from season 1 to whatever is next. So when the serial is detected in the <channel> it should signal to apps to display the episodes differently than episodic shows.
[ ] Group episodes by <itunes:season> numbers and allow for navigation between seasons
[ ] Display each season's episodes in the order set by the <itunes:episode number> tag in ascending order
[ ] Put show/season trailers (<itunes:type>trailer) episodes at the top of the feed/show listing/season listing
[ ] Move bonus episodes (<itunes:type>bonus) episodes to the bottom of the feed/show/season listing
[ ] Use the season and episode numbers to display "S1E9" or something like that along with the of each episode. (Or, if <code><itunes:title></code> exists, use that, as it's less likely to have season/episode descriptors in the title, though certainly not always) Those are the biggies. And please also scan for the new <code><podcast></code> namespace tags that replicate this. I use Apple's tags because they're more universal.</li> </ul> <p>Nice to haves for fiction podcasters (and others):</p> <ul> <li>[ ] If <code><link></code> tags are used with the <code><item></code>, display "get more info on this episode" or something like that</li> <li>[ ] Display episode-level tags if <code><img></code> tag found in <code><item></code>s</li> </ul> <hr /> <p>note from umbrafen in our Matrix space:</p> <blockquote> <p>sometimes the pocast uploads a new season trailer alongside the first episode and the order is wrong, so a more systematic approach would help season>trailer>episode1 would be the right order</p> </blockquote> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/evoterra"><img src="https://avatars.githubusercontent.com/u/2339588?v=4" />evoterra</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <p>It me!</p> <p>A quick comment on the prevalence of <code><itunes:foo></code> tags: I know there's a movement—which I support—to replicate those proprietary tags with <code><podcast:foo></code> tags. So whatever is done that keys off the Apple tags should also be scanning not-Apple tags, adjusting as the RSS2.0 spec changes. Please and thank you!</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/mitchdowney"><img src="https://avatars.githubusercontent.com/u/2262919?v=4" />mitchdowney</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <p>hey @ryanhirsch, @evoterra has a comment above I think would relate to <a href="https://github.com/RyanHirsch/partytime">podcast-partytime</a> handling.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/evoterra"><img src="https://avatars.githubusercontent.com/u/2339588?v=4" />evoterra</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <blockquote> </blockquote> <p>I like parties. </p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/RyanHirsch"><img src="https://avatars.githubusercontent.com/u/1883231?v=4" />RyanHirsch</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <blockquote> <p>It me!</p> <p>A quick comment on the prevalence of <code><itunes:foo></code> tags: I know there's a movement—which I support—to replicate those proprietary tags with <code><podcast:foo></code> tags. So whatever is done that keys off the Apple tags should also be scanning not-Apple tags, adjusting as the RSS2.0 spec changes. Please and thank you!</p> </blockquote> <p>Any links you can share related to this discussion? I'm trying to clean up some of the code internal on partytime right now, so if I need to make changes like this, its good for me to keep in mind so that new stuff plays well.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/evoterra"><img src="https://avatars.githubusercontent.com/u/2339588?v=4" />evoterra</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <blockquote> <p>Any links you can share related to this discussion?</p> </blockquote> <p>I am likely very little help, Ryan, as I'm a) not a developer and b) not entirely sure what partytime is supposed to do. But if there are links or other info I can provide that would help, I'm here to help. My call with Mitch last week was to discuss making Podverse work better with podcasts that have <code><itunes:type>serial</itunes:type></code> in their <code><channel></code> section, with a follow on to say "hey, don't forget that there are a bunch of <code><podcast></code> tags coming that will mirror (or be better than) the current Apple tags." </p> <p>But if you need samples of RSS feeds with said tagging, I've several hundred in a spreadsheet. </p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/RyanHirsch"><img src="https://avatars.githubusercontent.com/u/1883231?v=4" />RyanHirsch</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <blockquote> <p>not entirely sure what partytime is supposed to do</p> </blockquote> <p><a href="https://github.com/RyanHirsch/partytime">Partytime</a> is the RSS parser Podverse uses. So any initiatives to fully "clone" the <code>itunes</code> namespace under the <code>podcast</code> one, would require changes to it. Its a project maintained by myself, but originally "forked" from the podcast-index parser.</p> <p>I hadn't seen any discussion around cloning/duplicating the whole <code>itunes</code> namespace, so if you have any additional documentation or links to where this is going on, I'd appreciate it. I want to ensure partytime is kept up-to-date as much as possible. </p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/evoterra"><img src="https://avatars.githubusercontent.com/u/2339588?v=4" />evoterra</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <blockquote> <p>I hadn't seen any discussion around cloning/duplicating the whole <code>itunes</code> namespace, so</p> </blockquote> <p>I'm not sure how many of those conversations happened here on GitHub, Ryan. Or how many of them are "official," but if I see any that warrant linking, I'm on it!</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/mitchdowney"><img src="https://avatars.githubusercontent.com/u/2262919?v=4" />mitchdowney</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <p>@RyanHirsch I just sent @evoterra an email asking if he could share the spreadsheet of fiction RSS feeds, so I should be able to provide you with examples.</p> <p>In the meantime, here is an RSS feed I found that uses the <code><itunes:season></code> and <code><itunes:episode></code> tag, <em>however</em> I don't see a <code><itunes:type>serial</itunes:type></code> tag in it.</p> <p><a href="https://feeds.acast.com/public/shows/edd6bde5-221e-4c07-bde8-2a0241ccc6e0">https://feeds.acast.com/public/shows/edd6bde5-221e-4c07-bde8-2a0241ccc6e0</a></p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/RyanHirsch"><img src="https://avatars.githubusercontent.com/u/1883231?v=4" />RyanHirsch</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <blockquote> <p>@RyanHirsch I just sent @evoterra an email asking if he could share the spreadsheet of fiction RSS feeds, so I should be able to provide you with examples.</p> <p>In the meantime, here is an RSS feed I found that uses the <code><itunes:season></code> and <code><itunes:episode></code> tag, <em>however</em> I don't see a <code><itunes:type>serial</itunes:type></code> tag in it.</p> <p><a href="https://feeds.acast.com/public/shows/edd6bde5-221e-4c07-bde8-2a0241ccc6e0">https://feeds.acast.com/public/shows/edd6bde5-221e-4c07-bde8-2a0241ccc6e0</a></p> </blockquote> <p>👍 ill take a look later tonight </p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/RyanHirsch"><img src="https://avatars.githubusercontent.com/u/1883231?v=4" />RyanHirsch</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <blockquote> <p>👍 ill take a look later tonight</p> </blockquote> <p>So I see that partytime is correctly grabbing <code>itunesSeason</code> and <code>itunesEpisode</code> for each one of these items and that if the feed does have the <code>itunes:type</code> tag, I have the expected code to grab it and populate <code>itunesType</code> on the parsed feed. I have passing tests to detect episodic and serial as well.</p> <pre><code class="language-ts"> it("extracts node value (episodic)", () => { const xml = helpers.spliceFeed( feed, ` <itunes:type>episodic</itunes:type> ` ); const result = parseFeed(xml); expect(result).toHaveProperty("itunesType", ItunesFeedType.Episodic); }); it("extracts node value (serial)", () => { const xml = helpers.spliceFeed( feed, ` <itunes:type>Serial</itunes:type> ` ); const result = parseFeed(xml); expect(result).toHaveProperty("itunesType", ItunesFeedType.Serial); });</code></pre> <p>Right now things look good on my side. It seems like these feed either need to properly set <code>serial</code> or podverse should infer it based on some rules.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/evoterra"><img src="https://avatars.githubusercontent.com/u/2339588?v=4" />evoterra</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <p>A list of several hundred fiction podcast RSS feeds for you, @RyanHirsch and @mitchdowney.</p> <p><a href="https://docs.google.com/spreadsheets/d/1dwDwNSGvVhEWTjspIT-CxycD3D3h0rMOlSyUqEnw04A/edit?usp=sharing">https://docs.google.com/spreadsheets/d/1dwDwNSGvVhEWTjspIT-CxycD3D3h0rMOlSyUqEnw04A/edit?usp=sharing</a></p> <p>I'm not promising all of these have the <code>>serial<</code> tag properly set up, or have any of the <code>season></code> or <code>episode></code> or even <code>episodeType></code> fields property declared. In fact, many will not. So you'll get plenty of passes and fails.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/RyanHirsch"><img src="https://avatars.githubusercontent.com/u/1883231?v=4" />RyanHirsch</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <blockquote> <p>I'm not promising all of these have the <code>>serial<</code> tag properly set up, or have any of the <code>season></code> or <code>episode></code> or even <code>episodeType></code> fields property declared. In fact, many will not. So you'll get plenty of passes and fails.</p> </blockquote> <p>No problem! This is a great starting point to validate when things are "correct" in the feed partytime is doing the right thing, and if the feed isn't in the ideal state, it make give hints for how podverse can infer/guess that it could be serial.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/mitchdowney"><img src="https://avatars.githubusercontent.com/u/2262919?v=4" />mitchdowney</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <p>@evoterra @RyanHirsch so I'm looking at Serial's RSS feed, which I thought might be a textbook example of how a "serial" feed should implemented...but the<code><itunes:type></code> value is <code>episodic</code> instead of <code>serial</code>.</p> <p>Could this be an example of a situation where, despite the feed not properly declaring itself as of the <code>serial</code> type, perhaps we should handle the feed as if it were <code>serial</code> anyway? If yes...then @RyanHirsch I'm wondering if this is something we could pass an option to podcast-partytime, so that it does some duck-typing to return <code>serial</code> (or a 3rd type option) even if the feed specifies <code>episodic</code> or does not specify an <code><itunes:type></code>. What do you think?</p> <p><a href="https://feeds.simplecast.com/xl36XBC2">https://feeds.simplecast.com/xl36XBC2</a></p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/evoterra"><img src="https://avatars.githubusercontent.com/u/2339588?v=4" />evoterra</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <blockquote> <p>Serial's RSS feed, which I thought might be a textbook example of how a "serial" feed should implemented...but</p> </blockquote> <p>Yeah, that way lies madness! Serial podcasts existed long before the <em>Serial</em> podcast, like all the way back in 2005, when I started Podiobooks•com. And well before Apple gifted us the <code><iTunes:type></code> tag. And Serial came out a good three years before the tag was implemented, and, like most podcasters, the <em>Serial</em> team never bothered to update their feed with the new info.</p> <p>Personally, I don't think you should spend a lot of time on the exceptions here. With the exception of Spotify for Podcasters (was: Anchor), every podcast hosting platform allows for the feed type to be flipped from <code>episodic</code> to <code>serial</code>. But that's up to you, Mitch.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/mitchdowney"><img src="https://avatars.githubusercontent.com/u/2262919?v=4" />mitchdowney</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <p>@evoterra thanks for the background. My hunch so far is it seems like any podcast that is using seasons AND episode numbers could be treated as "serial" podcasts, as far as our UX is concerned.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/evoterra"><img src="https://avatars.githubusercontent.com/u/2339588?v=4" />evoterra</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <blockquote> <p>any podcast that is using seasons AND episode numbers could be treated as "serial" podcasts...</p> </blockquote> <p>Maybe. Though I know shows exist (my old one, as an example) that are episodic but still group episodes into seasons with sequential numbering. Shows that take a break over the summer, or just put out a series of like 12 episodes each year.</p> <p>Happy to share some RSS feeds of non-serialized shows that use S and E if you need it.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/mitchdowney"><img src="https://avatars.githubusercontent.com/u/2262919?v=4" />mitchdowney</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <p>@evoterra ok...and sorry you probably already explained this already, but if I'm understanding correctly:</p> <p>1) If a podcast has seasons + episode for its items, then group them in the UI in a hierarchy by season.</p> <p>2) If a podcast has <code>serial</code> declared, then the default setting of the sorting for that podcast in our UI should be chronological order, instead of reverse chronological order.</p> <p>3) For a combination of 1) and 2) do both.</p> <p>If that's the case, then @RyanHirsch we won't need special duck-typing from podcast-partytime.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/evoterra"><img src="https://avatars.githubusercontent.com/u/2339588?v=4" />evoterra</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <ol> <li>Yes, probably with "most recent" first, as with standard episodic podcasts</li> <li>Yes. And if no seasons or episodes are declared, just sort by <em>forward</em> chronological order, I guess.</li> <li>Yes! (This is the ideal state for fiction podcasts, true crime, docseries, and more.)</li> </ol> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/mitchdowney"><img src="https://avatars.githubusercontent.com/u/2262919?v=4" />mitchdowney</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <p>@evoterra thanks for clarifying </p> <p>And oof...this keeps getting more complicated...now I'm noticing that the Serial RSS feed has <code><itunes:season></code> set on items, but it doesn't have <code><itunes:episode></code> to tell us the episode number for each season...even though the titles contain an episode number :[</p> <p>Maybe I just won't use <code><itunes:episode></code> in v1 of this feature, and will group episodes together by season either in serial (chrono) or non-serial (reverse-chrono) order, but not try to do additional sorting by <code><itunes:episode></code>. I think that should be fine for most cases, and if edge cases are discovered where episodes are out of order within the RSS feed for a season, I'll cross that road when we get to it.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/evoterra"><img src="https://avatars.githubusercontent.com/u/2339588?v=4" />evoterra</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <p>I think, @mitchdowney, that if you try to make a single show from 2014 that published episodes before any of these tags existed look perfect, you're gonna have a bad time. Ignore the show managed by someone at the NYT is my advice. Or treat it as an exception.</p> <p>There are many, many serialized shows that have spent a great idea of time re-tooling their feeds with season and episode numbers to give a much, much better listener experience than can be provided by chronological or reverse-chronological order. It's your app, and you can make the final decision, but I'd hate to see it go down a weird path instead of rewarding creators (and delighting listeners) for doing all the right things.</p> <p>Group by season. Sort by episode number. That's the best path forward for listeners.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/mitchdowney"><img src="https://avatars.githubusercontent.com/u/2262919?v=4" />mitchdowney</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <p>@evoterra an initial mobile app implementation of this is now available in the 4.14.0 Beta release for iOS and Android (<a href="https://podcastindex.social/@podverse/110529063127583397">Join Beta</a>). </p> <p><em>However</em>...I've already seen an example where this implementation is breaking the display of content that previously displayed correctly 😣</p> <p>Correct:</p> <p><img src="https://github.com/podverse/podverse-rn/assets/2262919/67b82310-e5a5-4b96-b088-915544997530" alt="image" /></p> <p>Incorrect:</p> <p><img src="https://github.com/podverse/podverse-rn/assets/2262919/aeb9c26e-5418-4265-aeb3-a5d8553ade20" alt="simulator_screenshot_605EF226-0527-4AE5-B9D6-063112134FD3" /></p> <p>After investigating, it appears the 2nd podcast isusing the <code><itunes:season></code> tag incorrectly, in multiple different ways, that will be impossible for us to rectify in an automated way on our side. Here is the RSS feed: <a href="https://feeds.megaphone.fm/KHWTP7757216280">https://feeds.megaphone.fm/KHWTP7757216280</a></p> <p>The issue is serious because I can't even find the most recent episode for this podcast due to the invalid use of tags. It appears much lower in the list than anyone would expect.</p> <p>So this is a difficult problem to resolve...on one hand, it's the podcaster / RSS host's fault the feed is not following the <code><itunes:season></code> and <code><itunes:episode></code> tags correctly. On the other hand, Podverse listeners are not going to know this is a podcaster problem, not a Podverse problem. (For example, we receive bad reviews because we have "too many ads" when we literally have a policy against adding any advertisements of our own.)</p> <p>That said, I don't want to scrap the Seasons feature entirely. The only workaround I can think of is to manually flag podcasts in our database with invalid Seasons usage, and disable the Seasons feature for those podcasts. As for whether this manual process of flagging will be feasible for us though will depend on how widespread invalid season/episode tag usage is.</p> <p>Anyway, I expect 4.14.0 to be in prod within the next few days, and I'm going to focus on adding the flagging and website implementation tonight.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/evoterra"><img src="https://avatars.githubusercontent.com/u/2339588?v=4" />evoterra</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <p>So color me confused, @mitchdowney, but Kyrin's show, <em>Value 4 Value</em>, isn't <code>serial</code>, so I'm not sure why that one is used as a "good" example. </p> <p>Neither is <em>Who Are These Podcasts?</em>, which furthers my confusion.</p> <p>Perhaps the most straightforward implementation would be to display 'serial' content differently than 'episodic' (or undefined) content. Then, once that relevant subset of shows designed to be listened to by season and episode order has been optimized, you could decide what, if anything, to do about episodic shows that use season and episodes.</p> <p>(Quick hot take on that last bit: It's a combined fault between the creator and their hosting platforms to cock up the numbering of either seasons or episodes. Not sure I'd spend lot of time figuring out how to fix their screw-up when the best answer is to fix the feed.)</p> <p>Edit: Just drawing attention back to the title of this issue: <strong>Update the Podcast screen UX <em>for podcasts with the "serial" RSS tag</em></strong></p> <p>Emphasis added.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/mitchdowney"><img src="https://avatars.githubusercontent.com/u/2262919?v=4" />mitchdowney</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <blockquote> <p>Kyrin's show, Value 4 Value, isn't serial, so I'm not sure why that one is used as a "good" example.</p> </blockquote> <p>Ok, it seems I misunderstood. When I outlined <a href="https://github.com/podverse/podverse-rn/issues/1883#issuecomment-1728574070">in this comment here</a>, I tried to say in 1) that we would be implementing a seasons feature <em>even for shows that don't have the serial tag</em>. I intended for 3) to mean shows that have both seasons and serial implemented.</p> <p>In any case, if the <code><itunes:feedType>serial</itunes:feedType></code> is a reliable indicator that a feed intends to be rendered in Seasons, and isn't just incidentally using season + episode due to a misinterpretation of what the tag is for. I'll give the season + serial requirement a try, and hopefully we'll see better results.</p> <blockquote> <p>(Quick hot take on that last bit: It's a combined fault between the creator and their hosting platforms to cock up the numbering of either seasons or episodes. Not sure I'd spend lot of time figuring out how to fix their screw-up when the best answer is to fix the feed.)</p> </blockquote> <p>Yes, in this case it <em>is</em> the fault of the podcaster and/or RSS host company for allowing invalid feeds, but <em>our listeners</em> by and large do not understand that. If Podverse looks broken, people blame Podverse. We have numerous 1-star reviews for "too many ads" in Podverse, even though we have a policy against ever adding our own advertisements to Podverse or podcast content. We have to keep our listeners' perspective in mind when implementing new features. Unfortunately we have to weigh these concerns.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/evoterra"><img src="https://avatars.githubusercontent.com/u/2339588?v=4" />evoterra</a> commented <strong> 1 year ago</strong> </div> <div class="markdown-body"> <blockquote> <p>if the <code><itunes:feedType>serial</itunes:feedType></code> is a reliable indicator that a feed intends to be rendered in Seasons...</p> </blockquote> <p>The <code><itunes:feedType>serial</itunes:feedType></code> is a reliable indicator that the <strong>feed intends to be rendered as serialized content</strong>, starting with the first episode rather than the most recent. Additionally, if there are seasons (there need not be), then group said episodes, starting each season with the first episode of said season.</p> <blockquote> <p>If Podverse looks broken, people blame Podverse.</p> </blockquote> <p>Understood. Which is why I strongly suggest not trying to "fix" this across all possible podcasts and instead focus on those with <code><itunes:feedType>serial</itunes:feedType></code>. </p> </div> </div> <div class="page-bar-simple"> </div> <div class="footer"> <ul class="body"> <li>© <script> document.write(new Date().getFullYear()) </script> Githubissues.</li> <li>Githubissues is a development platform for aggregating issues.</li> </ul> </div> <script src="https://cdn.jsdelivr.net/npm/jquery@3.5.1/dist/jquery.min.js"></script> <script src="/githubissues/assets/js.js"></script> <script src="/githubissues/assets/markdown.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/highlight.min.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/languages/go.min.js"></script> <script> hljs.highlightAll(); </script> </body> </html>

podverse / podverse-rn

Update the Podcast screen UX for podcasts with the "serial" RSS tag #1883