Post B1efsXbPf1pG3WNang by nathan@xoxo.zone
(DIR) More posts by nathan@xoxo.zone
(DIR) Post #B1eE16M1XayZR8TVy4 by mitch@podcastindex.social
2025-12-26T17:32:38Z
0 likes, 0 repeats
The Podcast Partytime JS library that @RyanHirsch made has been working great for us, but it needs a few (I think light-weight) updates to get us past some blocking limitations.One of the issues is that Partytime doesn't parse the "list" medium types, which is an issue for list feeds that people like @ChadF make.https://github.com/RyanHirsch/partytime/issues/61Ryan has done amazing work but I'm not sure if he is still able to maintain it. https://github.com/RyanHirsch/partytime/issuescc @nathan @steven @suorcd @dave @adam
(DIR) Post #B1eE18H8OkFlOYCdcm by mitch@podcastindex.social
2025-12-26T17:36:24Z
0 likes, 1 repeats
@RyanHirsch @ChadF @nathan @steven @suorcd @dave @adam So I'm wondering, Ryan would you like to continue maintaining Partytime, or should we move forward with a fork?And if we do fork it, does anyone else want to be the maintainer?I can bring it under the Podverse org umbrella, and I don't think it would be overwhelming bc Partytime seems to do 99% of what it needs to already, but if someone else would like to be the maintainer, we'd certainly appreciate it.
(DIR) Post #B1efsUbIoyxGkJIxiC by nathan@xoxo.zone
2025-12-26T18:12:27Z
0 likes, 0 repeats
@mitch Have you seen the new thing that Dave and Eric have been working on?https://github.com/Podcastindex-org/feedparser
(DIR) Post #B1efsVwxnvsMvmRm76 by mitch@podcastindex.social
2025-12-26T18:35:06Z
0 likes, 0 repeats
@nathan I have seen it. I'm open to using it at some point, but podcast-partytime works well with our full-stack JavaScript infrastructure.I'm thinking it would take me a day of work to add the missing pieces we need to podcast-partytime, but switching to feedparser which is written in Rust would be a bigger initiative.partytime logic is only used in podverse-parser/src/lib/compat and podverse-parser/src/lib/rss, so swapping it out doesn't seem crazy difficulthttps://github.com/podverse/podverse-parser/blob/v5-develop/src/lib/rss/channel/channel.ts
(DIR) Post #B1efsWi6ydadI0VQbQ by mitch@podcastindex.social
2025-12-26T18:38:16Z
0 likes, 0 repeats
@nathan but also...partytime just seems really stable for our purposes, so I'm not sure if it is worth it for us to break from our full-stack JS pattern to incorporate feedparser/Rust. Also partytime uses Typescript types which is good for our builds and workflow.Anyway, if no one else is eager to maintain partytime, I think I will fork it tomorrow, make the changes needed, and maybe longer term start a migration to feedparser. I see you made some PRs that are not merged and I can take a look.
(DIR) Post #B1efsXbPf1pG3WNang by nathan@xoxo.zone
2025-12-26T18:52:30Z
0 likes, 0 repeats
@mitch yeah, we’re running similar stacks. I’m happy to contribute to your fork if you don’t mind some PRs that won’t be especially relevant to Podverse. I was planning to get podcast:follow tag support working soon (example feed: https://feeds.feedburner.com/radiotopia-showcase)
(DIR) Post #B1efsYVmHSucsKkbei by dave@podcastindex.social
2025-12-26T23:02:42Z
0 likes, 0 repeats
@nathan @mitch Makes sense you would stay with what works for you. I'm hopeful the new stuff will be transparent and just output data without needing to know what is going on behind the curtain too much. That's the goal anyway. Just spin up a docker and let her rip.
(DIR) Post #B1emYCq3qjXdXtTvpQ by mitch@podcastindex.social
2025-12-27T00:17:34Z
0 likes, 0 repeats
@nathan @dave we should be able to integrate with the Rust parser outputs. I think we may want a layer of Typescript types to go with the output. That’s just a data mapping exercise tho, and not strictly necessary.