All the reasons you gave are all the reasons I took on this project for sure. Thanks for giving it a go! Let me know if you have any troubles with the setup.
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.
Fantastic suggestion! I'll add it to the short term roadmap. Alternative auth options like github among others was already on the roadmap but if I can just kill all the birds with one stone that's great! Thank you for this.
I was thinking about that recently. Seems like it could be a decent use case for an Ai or something. A model that searches for consistent keywords or something. It's on my feasibility map to take a look at.
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.
I'm ever continuing development on my self hosted podcast management app with all the features you're looking for here https://github.com/madeofpendletonwool/PinePods
It's not in a finished state yet. But it's definitely usable as is. It's fully dockerized and hosted on your server, and streams from your server to clients.
It's not there quite yet. But give my project Pinepods a star on Github.
https://github.com/madeofpendletonwool/PinePods
The functionality you're looking for it coming. It will be able to stream from one device to another on a local network. Sort of a share function. I just released the first official beta version two days ago. There's currently a client and web version with a backend you can connect to with as many users as you want. I'm also planning to release an optimized client to share to likely built in rust for platforms with less power like Raspberry Pi's
Thanks for the suggestion on snipd. I'll check it out. Could be some good inspiration for features to implement.
It's now up at https://try.pinepods.online.
Feel free to try it out. Currently updating documentation with this url
Correct, I'm working on getting the example server up. It'll be up shortly and I'll update the link. Apologies for that
Hey! Thanks for checking it out.
-
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.
-
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.
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.