continuo: play now from Everything
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- kotlin
- Domain
- audio-video-rtc, mobile
Research direction
Start by reading the parent issue #50, the design in continuo#10, and the existing ResolvingDataSource flow for queue items. The issue describes coordinating a high-priority Soulseek download, streaming its growing file, and showing a waiting state, but does not identify files or tests. Done means the first track can start playing while the rest downloads, with the stated loading message and realistic startup expectations.
Written by the indexing model from the issue text.
Description
Part of #50. Play a track that isn't in the library yet: a high-priority request whose first file plays while the rest downloads. continuo serves the growing file (continuo issue below); Polyphony resolves stream URLs at load time (ResolvingDataSource), so the queue item just waits for it, with a visible "Starting from Soulseek…" state. Designed from continuo#10's latency per source; realistic time to first sound is tens of seconds from Soulseek, so no Spotify-instant promise.
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 0
- Avg merge
- 30m
- Merged PRs (30d)
- 62
Getting set up
- Ships a Dockerfile or Docker Compose file
- No 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 isaacault/polyphony
-
area/library area/ui priority/p1 type/feature
Difficulty 4/5 3-5 days Newbie friendliness 48/100
isaacault/polyphony#145 · 1 comment ·
Maintainers usually reply within 1 day
-
area/cast priority/p2 type/verification
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
area/playback priority/p2 type/feature
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
area/transcoding priority/p2 type/feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
area/transcoding area/ui good first issue priority/p2 type/feature
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Maintainers usually reply within 1 day
All issues in isaacault/polyphony
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Kotlin/kotlinx-io#529 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
mcnaveen/health-connect-webhook#110 ·
Maintainers usually reply within 1 day
-
Delete all aboveOpenenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mjaakko/NeoStumbler#1307 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
tanujnotes/Olauncher#770 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100