Ideas for the API
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
No files, tests, or concrete acceptance criteria are identified. Start by reviewing the current scraper and the paginated /videos/n endpoint, then choose one proposal, such as deeper channel scraping or engagement-based ordering. Before implementation, define the required behavior and what constitutes a complete result.
Written by the indexing model from the issue text.
Description
We are about to deploy the initial version of the API which currently provides data for the awesome-manim feed on the website (corresponding PR for the website https://github.com/ManimCommunity/manim-website/pull/73)
The scraper currently:
- fetches the list of all YouTube channel links from the README file
- scrapes the publicly available RSS feeds that are available from
https://www.youtube.com/feeds/videos.xml?channel_id=xxxxxxx. - searches for the substrings
Manim(case insensitive),#some(case insensitive),SoME(case sensitive) in the video title or description. When found, the videos are marked as "being manim videos". - The scraper then puts them on a MySQL database and serves videos chronologically on a paginated endpoint
/videos/n, 30 videos at a time.
This issue records some ideas we could implement in the future based on feedback.
- A deeper scrape of all the channels (RSS feeds just return the latest 15 videos)
- An algorithmic feed that prioritizes videos with higher engagement, but still retains the chronological ordering to some degree
- ...
Feel free to discuss these and propose any other ideas.
- Dominant language
- Python
- Stars
- 5
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
Similar issues
-
docs(types): update the collection binding note now that typed collections shipped in pycubrid 1.9.0Opendocumentation priority: low size: S
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cubrid-lab/sqlalchemy-cubrid#768 ·
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 65/100
ansys/pydpf-core#3547 ·
Maintainers usually reply within 1 day
-
core
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
vectorize-io/hindsight#5457 ·
Maintainers usually reply within 1 day
-
[Bug]: LangChain drops OpenAI Responses text blocks from session recordingPossibly taken @ktz03 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
volcengine/OpenViking#5806 ·
Maintainers usually reply within 1 day