Podcast CLI player

CPU usage averaged 14 - 15% on my computer which is unreasonably high. Now it's more like 4%. You can get lower if you go above 16 ms (2 - 3% at 50 ms) but this seems like a good place to start. Also I restructured the code to be marginally more efficient because its a hot path

Thank you for the great app!

Currently, the app does not support "play next" functionality, but it would be quite useful to have that so that users do not need to select what to play next every time a story ends.

Thanks.

Hello,

What an awesome project!

I would really like some command line options so I could start playing an episode from the command line, eg pocast-cli --rss https://rss.whooshkaa.com/rss/podcast/id/12924 This would start playing the latest episode, or you could play an older one using an offset switch, eg pocast-cli --rss https://rss.whooshkaa.com/rss/podcast/id/12924 --offset 5

hi if you download an episode and exit, you should download that episode again in next time. i think podcast-cli should save file on disk and read that from disk for the next time.

• make the program not panic on bad search queries (which breaks some terminals)
• make the program fail to run when given invalid arguments
• add podcast-cli and Vim files to .gitignore
• consistency changes ([]*Episode{} -> make([]*Episode, 0), etc)
• slice pre-allocation optimizations
• formatting changes

When selecting a podcast category I receive the error Design (Current date and time when selected) Authorization access token is not found

I am assuming that your Itunes-API token has been revoked for some reason.

• [x] Make an API that uses another podcast services under the hood (probably Apple podcasts)
• [x] Integrate the new API with Podcast-cli :
  • [x] Update the Podcast and Episode structures
• [x] Refactored the ui package

Can we add our own podcast sources from rss and keep them? I avoid anything apple for moral and ethical issues. so dont want to stream from itunes, will like to add my own and remove itunes thanks

an important part of podcast player is remember position feature ( think about a 3 or 4 hours episode) i think it can be so helpful if podcast-cli can remember last position in this different situation:

1. if you play/pause an episode
2. if you play another episode in middle of other playing episode
3. if you close podcast-cli

it can be so useful ,if you can add this feature for every episode (not only for last episode)

one of advantage of go is the speed podcast-cli try to get rss data everytime you launch that. this method has two important Cons

1. if you don't have access to the internet you can't use that
2. startup time is so slow

for a better experience:

1. it is better to podcast-cli save data in a local database (something like sqlite).
2. podcast-cli read data from local database and load ui.
3. when load database and gui finish, it try to update feeds in background.

it make startup time so much faster