How to Use Privacy Redirect for Firefox: Nitter, Invidious & More

Configure Privacy Redirect for Firefox — Best Instances and Settings

What Privacy Redirect does

Privacy Redirect is a browser extension that transparently redirects requests to social media and tracking-heavy services (Twitter/X, YouTube, Instagram, Reddit, etc.) to privacy-preserving frontend instances (Nitter, Invidious, Libreddit, etc.). It runs locally in your browser and uses rules to replace URLs so you interact with lightweight, less-tracking interfaces.

Recommended frontend instances (examples)

• Twitter/X → Nitter
  • nitter.net (popular, sometimes rate-limited)
  • nitter.snopyta.org
  • nitter.kavin.rocks
• YouTube → Invidious / Invidious instances
  • yewtu.be
  • yewtu.cafe
  • yewtu.cafe/watch (instance availability varies)
• Instagram → Bibliogram / InstaDP alternatives
  • bibliogram.art
  • biblio.social
• Reddit → Teddit / Libreddit
  • teddit.net
  • teddit.cafe
  • libredd.it (instance-dependent)
• Mastodon / ActivityPub → alternative frontends
  • foss.social (instance for Mastodon)
  • fediverse.party (directory; use specific instance URLs) Note: Instances go up/down; pick a few healthy alternatives.

How to configure in Firefox (prescriptive steps)

1. Install Privacy Redirect from the Firefox Add-ons site.
2. Open the extension’s options page (Extensions menu → Privacy Redirect → Options).
3. Review the built-in rule list; enable the rules you want (Twitter, YouTube, Instagram, Reddit).
4. For each service, add 2–3 instance URLs in the extension’s replacement list (primary, fallback).
   • Example rule for Twitter/X:
     • Match: https://twitter.com/and https://www.twitter.com/*
     • Replace with: https://nitter.kavin.rocks/$1 (or use the extension’s pattern syntax)
5. Prioritize fast, reliable instances as primary and keep backups to avoid breakage.
6. Enable “open redirects in same tab” or similar preference if available for seamless browsing.
7. Test by visiting a service URL; confirm it loads the chosen frontend and not the original site.

Settings recommendations

• Fallback list: Configure multiple instances per service to reduce failures.
• Respect embeds: If you need embedded media, allow direct opens for specific domains rather than redirecting.
• Per-site disabling: Whitelist sites (e.g., banking, sites requiring original behavior) to avoid breaking functionality.
• Auto-update rules: Enable automatic rule updates if the extension supports it to maintain compatibility.
• Privacy vs. functionality: If a frontend blocks features you need (e.g., login), selectively disable redirects for those pages.
• Custom rules: Add site-specific rules for regional domains (e.g., youtube.co.uk) and mobile subdomains.

Choosing instances — criteria

• Uptime: prefer instances with good availability and low latency.
• HTTPS support: must use HTTPS.
• No tracking: instance operators should respect privacy and avoid logging.
• Active maintenance: choose instances with recent updates or active maintainers.
• Geographic diversity: multiple regions reduce correlated downtime.

Troubleshooting

• If a frontend returns errors, try switching to a different instance.
• Clear cache and disable other privacy addons temporarily to check for conflicts.
• If media (video/audio) fails, open that link in the original site or use a different Invidious instance.
• Report broken rules to the extension’s issue tracker with example URLs.

Quick example table (service → example primary / fallback)

If you want, I can generate ready-to-paste replacement rules for Privacy Redirect for the specific instances above.