Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don't know if this is a good place for feature requests, but the only thing keeping me from switching to this at at the moment is download settings per podcast.

For example, some podcasts I don't want to miss an episode and I want them all downloaded. Other podcasts I only check in on occasionally and would only want the latest episode to be kept on device.

I subscribe to a lot of podcast and downloading and keeping every episode is going to eat up a lot of storage.

Besides that, love the simplicity of it. Well done!



I don't know if this is a good place for feature requests

If you've checked out the thing being showhn enough to have a feature request, you're doing Show HN right.


Thanks! That makes a lot of sense. It actually only downloads at most 2 episodes per podcast at a time, but that's still not great for your use case. I do plan to add per-podcast settings in probably the release after next, so stay tuned for that!


I have the same requirements but started to think these use cases might be different enough to warrant different apps. So I’ve gradually shifted to those “don’t miss” ones in a dedicated podcast app and the occasional ones to Spotify. Could probably do with another app for the tiny daily ones too..


I've considered the multiple apps to manage content consumption but it's such an inelegant solution I've been unwilling to try it.

I want to be able to categorize content. I want a category of podcast to work to, work out to, go to sleep to, or to simply sit a learn. I want different categories of music. I want to be able to set a group of content on YouTube that I will watch everything on, and one that I can sort through and pick the few videos I want to watch.

Given the value of that data in just my sorting and prioritizing of content, I don't know why I don't have the tools so that data can be harvested and sold.

I think it will lead to better content.


You don't need two apps – Overcast does all of this.


[flagged]


I don't see anything being demanded. I have several open source projects used by other people. I don't implement every requested feature, but requests are a great way to get ideas I might never have had on my own.

If a developer wants money for every feature, they're free to use a commercial license and accept the tradeoffs.


Demand or request – what gives somebody the right to make a request without offering anything in return? Most people here wouldn't walk around in the street asking strangers for a handout, or ask for free stuff in shops and restaurants. So why is it okay to make these requests without offering even token compensation?

I have made feature requests from open source project, and always with a monetary offer attached. If everybody who wants a feature pitches in a little, then the creator will be compensated fairly if he chooses to implement that feature.


I can recommend reading "The Cathedral and the Bazaar" if you're interested in learning more about the philosophical and economic underpinnings that existed in the early days of open source, which still largely hold true today.


You're misidentifying the interaction.

Person 1: I have built this thing that I hope you find useful.

Person 2: I can't use your thing unless it has this feature that my current thing has.

That is a two-way interaction, not a one-way demand. Person 1 is enriched by understanding what features might help them build a product people want.


I interpret the interaction like this:

Person 1: I have built this thing, maybe somebody finds it useful. Then you can have it for free. Person 2: I'm not going to use it unless you do as I say with your thing, and I'm not going to offer anything for you.

Well okay, then don't use it? Or if you want a feature, offer something in return. Or make the request towards a paid service – their ears are very eager to hear what features potential customers would like to have.


You have a cynical view of what is a feature of Show HN posts: community feedback. This is where the rubber meets the road and where you find out if people would use your project. And part of that is people telling you why they wouldn't use it.

The best case scenario really is that the only thing keeping someone from using your project is a feature that you can implement that would make your project better for everyone. For the sake of launching, you tend to pick a subset of features that you consider necessary, and it's good feedback when all you need to do is extend the circle to include a few more.

I think your negative reaction is warranted for when people trash the project, especially under the weak guise of constructive criticism. But feature feedback is not that.

The OP himself liked the feature request which is perhaps a counterpoint to your interpretation. I don't think they would agree with you that it was inappropriate nor demanding, but rather useful feedback.


One of the problems with open source hobby projects as opposed to projects you do for a job is the lack of feedback. If I ever were motivated to do an open source project to scratch an itch, I would want feedback and feature requests to make it better


It was a suggestion, not a demand or request




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: