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 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.

It's a carryover from the original project. I did a complete rebuild of the frontend at one point to wasm due to rust having good frontend support with Yew. I plan to rebuild the backend too. All in due time.

I'm likely to rebuild the backend in Go, and while there will be a speed difference to a degree, the api isn't sending complicated data. The bottleneck in response times usually isn't what you'd make up for using a lower level language. Usually it's more likely query times and Frontend processing. The Frontend rebuild MASSIVELY sped things up. Which is why I started there.

And yeah, doc site needs a refresh. I spend too much of my Pinepods time programming.

Excellent point, I will include communication around Podcast 2.0 and all it's features in the future.

Same reasons for any Self hosted projects. Own your data, Archive the content, I like Self-hosting. Pick your favorite reason. Podcasting is built to be an open platform. It deserves open and Self Managable clients.

You can, on your local device. Pinepods syncs progress between devices instantly. I like to switch between laptop and phones. If you only listen on your phone and the app works for you that sounds like a great solution already.

Hey! I'm the Developer of Pinepods. It really aims to be the ultimate podcast solution that's as self-hosted as possible. I'm trying to make it as fleshed out feature wise as any paid or android specific podcast application while allowing for server sync and access everywhere on any device. Its getting better and better all the time! https://pinepods.online/

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.

Absolutely true. And if you only listen to podcasts on your phone that's a great solution. I like to switch between phone and laptop, and Pinepods syncs progress of everything on any client nearly instantaneously.

Ugh.. It is unfortunate isn't it.. Here's the history of the name.

I started development on Pinepods back when I was learning about python's fastapi. It originally was built in pure python. And as you can probably imagine the UI was dog slow because python isn't exactly fast. At that point it was called Pypods. Because python. I wanted to then change the name away from being a reference to a programming language. Only the nerdiest people would get that, plus I wanted it to have it's own identity instead of being tied to a language. So I went with Pinepods, which itself is a reference to the pine snake (kept the snake thing despite moving away from python) and at that point I started adopting the forest theme. Which is why if you visit try.pinepods.online you'll see rotating images of pine forests.

At this point, it's been over a year and I've invested somewhat in the tree/forest idea. I would struggle to move away from it because I love the forest undertones.

Changing the name is feasible. And might be a good idea. It kinda stinks I'd need to change the domains along with it but I suppose it is what is there. The challenge that I struggle with is coming up with something that keeps the forest theming. I really like that aspect of it.

With the android App in Beta I'd continue using AntennaPods along with it. With Nextcloud/Gpodder sync or RSS feed exporting Pinepods is built to be great along with your current favorite apps. Not completely replace them. The goal is that it it could replace apps, but it doesn't have to. You should be able to listen however you want to.

It's a good thing my skin isn't made of coral.

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!

There's an offline mode on the clients to listen to downloaded episodes locally. That does not work on android just yet. That's part of what makes the android client beta. All the clients (including android) are built with Tauri, so they all build from the same code. It does however introduce some challenges when finding libraries that will compile to both desktop and mobile.

Yes absolutely. If you're using Pinepods between the two devices your listen time is synced to the server. Meaning swapping between devices syncs your exact listen time. In addition to that I almost have time sync implemented for nextcloud sync as well. Meaning swapping between antennapod and pinepods your listen time will sync also.

Pinepods 0.7.4 is out! So as the Dev I'm going through new issues and knocking them out. Smart playlists, oidc logins and notifications on release are all a thing now on the self hosted podcast platform! We're nearing a v1 release with features on par with some of the big time podcast apps.

Go is simpler to write and is great for apis. Also has strong library support for interacting with databases. That's the primary reason. They both create compiled binaries which means no library dependencies taking up space on the container. That's the primary issue with python currently. I have no problem using actix in rust and that might be a good direction to go honestly, the primary concern is removing the compile at runtime language.

That sounds like sleep. Not hibernate. Hibernate is the process of moving your working ram onto disk. It's similar to a full power off except your current state is saved. Hibernate doesn't usually work oob. Sleep does.

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.

Hey! Thanks for checking it out.

1. Not yet, but postgres support is coming in the very short term. I have been working to get it working and will have an update soon with support for it. I'll actually be on vacation for the next week, but I would anticipate 2 weeks before I have postgres working and a new version posted.

2. Excellent point. I had forgotten to add that to the compose file. When you download locally it adds files to /opt/pypods/downloads inside the container. So you could mount:

   volumes:

   • /home/user/pinepods/downloads:/opt/pypods/downloads

I'll add that to the compose file. Thanks for pointing that out.

As for layout, currently server downloads put them all in one downloads folder mass, however, on the client when downloaded locally it lays them out with podcastname, episodename structure. I'll get the server portion of that implemented as well.