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!

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

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.

I like it a lot. It’s not particularly difficult to write and once you get a feel for building components it’s pretty simple to conceptualize just about anything you’d need to build. I’d probably say difficulty is about the same to write react/svelte etc… Primary difference is that I don’t need to deal with webpack/npm dependencies. Absolute worst. web_sys support is great in rust and does absolutely everything you’d need to interact with a browser.

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.

Significantly upgraded just about everywhere. More features, supports modern podcasting 2.0 support, works great on mobile devices, sync support. The list goes on.

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.

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.

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.

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.

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.