Pinepods has smart playlists which sounds like it does what you need. Though I’m not 100% what you mean by ‘alternates between podcasts starting with oldest to newest’ but you can absolutely make a playlist sorted from oldest to newest. https://www.pinepods.online/docs/Features/smart-playlists

Can’t win em all :/ No matter what I do there’s always difficulty that comes from somewhere. Difficulty getting the app released in certain countries due to Apple’s strict rules, difficulty with people confusing pinepods with pine64s pinebuds and commenting on every post about it, difficulty with using .online domains now. I just picked the best available domain at the time. I really wish I had pinepods.com.

I’ll continue making the app the best it can be taking on one challenge at a time. There will always be blockers for some people for one reason or another.

Yep, it’ll come. One thing at a time for sure. The android app just released on the Google Play store a couple days ago so that’d a huge milestone to that end.

In the addition to everything the other commenter said, I would ask that you glance at the documentation briefly on the official site. There’s just a mind numbing number if features that set Pinepods and Audiobookshelf apart and there’s docs for just about all of it. Absolutely no shade, Audiobookshelf it’s a phenomenal project. But Pinepods is podcasts, that’s it’s entire identity, and it shows

https://pinepods.online/

Stay tuned in the very near future. All that sharing, beaming functionality is very shorterm roadmap stuff.

Hey thanks for selling it! 😀

Unfortunately no, admittedly bare metal server installs haven’t been a huge priority to me either because the containerization sets up some very important context that would be someone difficult to do outside it. Like proper routing between the frontend and backend for example. As they are both separate services. So like yeah, I could get it to work with enough time. But the instructions would be quite long for setup.

Hi! I’m the developer of this project. I probably would have written up a little of what pinepods is and who it’s for rather than a paste dump of the change log.

Pinepods is a podcast server that’s self hosted. It aims to be a multi-client version of what you might already have on your phone that allows you to listen anywhere. Host pinepods and get a web client, mobile apps, desktop apps, even a CLI app. Your progress syncs between all these. It supports gpodder sync for use with your existing apps if you want (though I’ve put 100 plus hours into the mobile apps and really would appreciate people at least giving them a go) and it has tons of features. Think Notifications on release, smart playlists, multi user, sharing, chapter support, YouTube channel to podcast support. Loads of stuff, and loads more still to come.

With 0.8.0 the mobile apps are now on Google Play and the Apple app stores, and the api has been fully rewritten in rust. It’s a lean mean podcasting machine. And actually the real current version is 0.8.1.

I appreciate the post OP but if you could, next time please add the above.

I suppose yeah. It’s better practice to use an env file for sure. No doubt there. I’ll get it on the list to update.

Appreciate you trying it out though!

I’d love to have it on F-Droid. Pinepods 100% checks all the boxes needed to be on F-Droid. They’ve stopped responding to me though: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/24866 It’s been rather frustrating. It will be on the IzzyOnDroid alternate F-Droid repo though as soon as 0.8.0 is out. And I’ll continue to make an effort to get it on F-Droid ASAP. Nothing I can do if they aren’t responding though.

And yep, the android/ios clients support local downloads in addition to the server downloads. So do the desktop clients. You are correct that currently local downloads only support one episode at a time though. That is on the list to change. All in due time, it’s a brand new app. :)

Yep for sure. Download progress is a top priority feature coming. It is still somewhat beta since its so new so expect some bugs here and there for sure. As well as some missing features still. For the record it doesn’t technically sync via the gpodderapi. Because this is an official pinepods client this syncs directly via the pinepods api that the web version also uses. This is far faster than doing incremental gpodder api syncs. It still works with gpodder api to other apps because the server side handles that but this app itself uses the pinepods api.

There’s also theoretical progress syncing with offline going back to online currently but I haven’t dug into the intricacies of validating that works yet. Expect more on fleshing that out in the very short-term.

I really appreciate the thoughts on it though! It’s really helpful to have direction in other’s podcast workflows. I genuinely don’t utilize many of the features that have been implemented into Pinepods because I’m a pretty simple listener, so without feedback I wouldn’t know what else people want.

Much appreciated! If you have thoughts on improvements or experience bugs I’d love to hear about it!

Thanks! And let me tell you on that front. What a frustrating experience F-Droid has been: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/24866 They’ve completely ghosted me. So far its looking more like it’ll be available in the F-Droid compatible IzzOnDroid repo. He’s been quite responsive and really helpful.

Correct, just use nightly for the moment and as soon as 0.8.0 is out either switch to that tag or use latest.

Aaannnd literally nothing. You mentioning that made me realize I forgot to remove the name field from the form template I used. Just put garbage in there, and I’ll change it. I only need an email. And even then it’s primarily for the Google variant that I need an email. If you are ios you can skip it completely and just use the test flight link if you want. https://testflight.apple.com/join/8Aax2BcX

Because of the Google play variant. Which requires I add an email. I don’t collect the email at all unless you check the box for news, and for the Apple one the form just sends you an email with the link in it. You can totally skip the form and just use the link. Here: https://testflight.apple.com/join/8Aax2BcX

Syncing from device to device. If you’d like to archive podcast episodes, say on like a NAS. Syncing of podcasts and episodes between apps and devices.

If you prefer to use one device for podcasts then Antennapods might be a good fit for you.

For me personally, not having to wait for podcast feeds to update on my local device alone is enough to sell Pinepods… Let alone the other benefits. Granted I’m biased.

Yep! The Android App is somewhat in the works. It compiles, works and has all the features of the web version currently. The things that don’t work are the aspects that make it an actual Android app. Like local device downloads and integration with Android APIs. That stuff is coming. After this next minor release getting to those are my priority.

Not that I’m biased or anything, but Pinepods objectively has WAYYY more features than audiobookshelf for podcast management. Because it’s a podcast server of course. Things like podcast 2.0 support with chapters, hosts, and transcripts, YouTube channel support, embedded podcast Index, YouTube and iTunes search support, external RSS feed support, etc. Audiobookshelf is great, but it’s an audiobook app. It’d probably be clutter to add a lot of this stuff.

And true on the link. It should redirect though.

Working on Smart Playlists for Pinepods I’m the developer of the self-hosted podcast management server and Sunday is always my new feature day. I’ve had a lot of fun adding in new features lately. Like designing a homepage and adding OIDC login support. Don’t let anybody tell you auth isn’t fun.

I get that comment often. I’ll change the name if I have to. But it’s a small open source project. My SEO results are already non-existent.

Exclusion filtering! What a great idea! You can quickly filter by keyword for episodes currently but you can’t exclude certain words. I will get exclusion filtering added. The code is already in place for it!