TeamNewPipe / TeamNewPipe/NewPipeExtractor
Support for opening `watch_videos` playlist URLs
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 602
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 6
Description
Describe the feature you want
Following a URL like
...redirects with HTTP response 303 to a URL like
https://www.youtube.com/watch?v=sjRTSkBHnyo&list=TLGGTxknVJuOq2MxNzA1MjAyMA
As far as I know, the URLs redirected to expire after a while. (I had this result years ago.)
NewPipe should be able to open these links by simply following the redirect. For me, opening means scanning the QR code of a watch_videos URL and selecting NewPipe as the app to open it with.
Should NewPipe ever save opened playlist URLs somewhere to make them available to the user again, it should save the watch_videos URLs in this case.
Is your feature request related to a problem? Please describe it
—
Additional context
How will you/everyone benefit from this feature?
Being able to scan QR codes with watch_videos URLs and open them with NewPipe, instead of having to follow the redirect before creating the QR code, makes the process more versatile. If your QR code scanner has a history, you can open the URL later when the URL originally redirected to may already have expired.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
The issue names no files or tests. Start by tracing the YouTube URL handling and redirect parsing in NewPipeExtractor, then identify how playlist URLs are recognized. Done means a watch_videos URL can be opened and its videos are handled as a playlist, with the original URL preserved if opened playlist URLs are saved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100