• 7 Posts
  • 33 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle








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


  • Extremely good call on the tagging. I love that. I’ve implementing saving for some basic essentially bookmarking of episodes so far but taking that one further and allowing the user to define custom save tags that they can associate without episodes and quickly access is a fantastic idea.

    I’ll have to give your backlog queuing idea some thought. I think there’s absolutely room for that feature. There’s also a lot to considering with implementing it in the most effective way possible. I wondering about maybe taking a look at what podcasts you listen to the most, checking which episodes from those you haven’t listened to, and then aggregating them into a cohesive backlog. These kinds of computational tasks like refreshing for example already happen on the backend so adding more things like that doesn’t affect the user experience at all.