Show the Podcast episodes in newest first order
Maintainers usually reply within 6 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 69/100
Research direction
Start by locating the code that loads and displays podcast episodes, then check where the 300-episode limit and feed ordering are applied. Use the linked RSS feed as a reproduction case; done means episodes appear newest first so the latest episodes are accessible.
Written by the indexing model from the issue text.
Description
Problem
Right now the Podcast episodes are show in feed order and up to 300 episodes.
One of RSS which I listen have around 2500 episodes and from the oldest to the newest so I can't see and listen the latest one.
The RSS is here and the website is here
Proposal
Show the episodes in newest first order instead of the feed order.
Mockups / references
- Dominant language
- Go
- Stars
- 4.4k
- Forks
- 307
- Avg merge
- 6d 16h
- Merged PRs (30d)
- 19
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bjarneo/cliamp
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
bjarneo/cliamp#681 · 1 comment ·
Maintainers usually reply within 6 days
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bjarneo/cliamp#520 · 2 reactions ·
Maintainers usually reply within 6 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
SAP/crossplane-provider-btp#1175 ·
Maintainers usually reply within 1 day
-
adk: stream concatenation errors bypass retry and failoverPossibly taken @OUAO-FRANK claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google/osv-scalibr#2586 ·
Maintainers usually reply within 2 days
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stacklok/toolhive-catalog#1890 ·
Maintainers usually reply within 1 day
-
heap: pushing an item that is already queued corrupts the indexPossibly taken @lbarrosby claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
kubernetes-sigs/kwok#1800 ·
Maintainers usually reply within 1 day