TeamNewPipe / TeamNewPipe/NewPipeExtractor
Use WEB_EMBEDDED_PLAYER with JS signature decryption to obtain playable stream URLs
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 2k
- Forks
- 602
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 6
Description
Checklist
- I am aware that this issue is being opened for the NewPipe Extractor, NOT the app, and my feature request will be dismissed otherwise.
- I made sure that there are no existing issues - open or closed - which I could contribute my information to.
- I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
Use WEB_EMBEDDED_PLAYER client together with JavaScript signature deobfuscation to obtain the real streaming URL.
Why do you want this feature?
serverAbrStreamingUrl is not directly playable
Additional information
No response
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, tests, or entry points. Start by locating the YouTube extraction code and tracing how serverAbrStreamingUrl is handled, then review the existing JavaScript signature-decryption approach. Done means obtaining a playable stream URL through the WEB_EMBEDDED_PLAYER client and covering the behavior with appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100