TeamNewPipe / TeamNewPipe/NewPipeExtractor
Thin backend layer between Extractor and NewPipe client?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 602
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 6
Description
Maybe the approach has already been considered in the past but since I couldn't find an issue about the same, I decided to make a fresh one.
Given we have no control over how frequently and/or drastically YouTube changes the way it serves its pages, maybe its worth considering writing a thin layer sitting between the extractor and the client? That way if and when the extractor starts failing due to changes made on YouTube's end, the client can still continue to consume a subset of "cached" content on the thin layer.
Not sure if there are any legal or miscellaneous blockades that stop us from doing this, but thought it was best to clarify by simply asking :)
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
No files, tests, or specific entry points are named. Start by mapping how the extractor currently serves the NewPipe client and review the repository history and issue discussions for prior consideration; this issue is done only when the feasibility and scope of a thin caching layer are clearly decided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100