Suggest a Frontend


  1. Open Source
  2. Enhances Privacy over main site
  3. Can be self-hosted. So, It's Decentralized
  4. Using it is really hard without automated redirections

Good Examples

Bad Examples

Why forking Privacy Redirect?

Privacy Redirect hasn't been maintained since 6/12/2021. Many instances are hard coded. Some should be removed as they became offline and many others should be added. Many Pull Requests were left pending and waiting. So we stepped in. Later, we started improving it further by adding new features and frontends.

Why all those permissions?

Let's examine them one by one:

Where the hell are those instances coming from?

Almost every frontend project has a list of public instances. Examples: Invidious' official instances list, Nitter's official instances list. For frontends that don't have an instance list, we use our own, which you can find under src/instances. We fetch those lists using an automated python script. This script gets triggered every 3 days. We don't intercept nor modify the lists outside of removing urls that are not valid (the structure is not that of a url) and removing trailing slashes. They're not our responsibility: they're the projects maintainers'.

Why not using a single reputable instance?

LibRedirect is just a tool. We're not here to choose for you. It's your own choice. The default setting selects all instances except those using Cloudflare, but you can change it yourself.

We can't know which instances are reputable for you and which aren't. Every person has a different point of view. LibRedirect should follow your point of view, not ours.

Chrome Web Store?

We can't publish it to the Chrome Web Store as it requires Manifest v3 and we use Manifest v2. You can still install it manually. We are planning to adopt Manifest v3 in Firefox as they will support the feature LibRedirect needs. If other browsers support Mozilla's policy, you might see LibRedirect in the Chrome Web Store.

Why not Manifest v3?

Read this:

What is Unify Settings?

This feature makes the use of multiple instances consistent by unifying cookie settings such as theme, language, etc.

To use it: visit one of your selected instances, go to its settings page, change its settings, then press "Unify Settings" in the popup. This will copy all the settings from the current instance and apply it to all the other selected instances.