Think I might undo this change — lots of people hate it:

"Making Unplayed areas exclude played episodes; formerly, ‘unplayed’ really meant ‘not deleted’”

This has confused people since 1.0 because “Unplayed” could include played episodes if you didn't use auto-delete.

I decided to finally fix the problem by making the behavior fit the labels — but a better solution may be to revert to the previous behavior and considering changing the labels to be more descriptive.

Maybe “Current” instead of “Unplayed”.

The loss of the Archive list mode has also irritated people, but the new All mode is popular, and having all 4 there is confusing and leaves too little room for the text label. Maybe I got rid of the wrong one.

I always want either Unplayed/Current for current stuff, or All when I want a giant alphabetical list to find something. But Archive was good for occasional decluttering.

Maybe I should bring Archive back, but get rid of Active.

Current, Archive, All.

I think this works really well…

If you've ever wondered why so many podcast apps have HUGE settings screens full of little nitpicky toggles, take a look at my mentions.

Everyone wants a slightly different set of often-conflicting behaviors, and there are tons of edge cases to consider with every decision.

@overcastfm I don’t mind larger settings screens if the settings are useful, well ordered and clearly described. I know that’s not what you’re going for, just saying.
@veith @overcastfm Even with many settings, there is still the problem of what the defaults should be. Many users do not venture into settings to change things, and if things don’t work the way they expect, they assume it’s broken. From a QA point of view, every new configuration creates a different set of combinations where something can break. So “just add more settings” should not be a default answer, regardless of ordering and description.
@ravenskana @overcastfm What did I say to make you think I don’t know that? Doesn’t change that I don’t mind a larger set of settings in the apps I use and that still can be valuable feedback for a developer I’d say. What they can and want to make of it is their decision then.