code-charity / code-charity/youtube

Invidious/alternative frontend redirect support

Open
#4,099 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature request Generated
Dominant language
JavaScript
Stars
4.6k
Forks
996
Avg merge
2d 15h
Merged PRs (30d)
7

Description

Feature Request: Invidious / Alternative Frontend Redirect

Description

Add option to redirect YouTube video URLs to alternative privacy-respecting frontends like Invidious, Piped, or CloudTube for ad-free, tracker-free viewing.

Why
  • RedirectMe (GreasyFork) — YouTube to Invidious redirect
  • YouTube to Invidious (GreasyFork) — dedicated redirect script
  • Privacy-conscious users want ad-free viewing without extensions
Preferred behavior
  • Toggle: redirect all youtube.com/* to chosen Invidious instance
  • Instance selector (public instance list or custom)
  • Auto-redirect button per video
  • Works for watch pages, channels, search

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the extension's YouTube URL navigation handling and settings UI. Trace how watch pages, channels, and search URLs are handled, then identify where redirect preferences and instance selection would fit. Done means the requested toggle, instance choice, custom instance support, and per-video redirect behavior work across the listed YouTube page types.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.