[Request] Remove kavin.rocks from https://redirect.invidious.io due to the cloudflare-gate

[Kreyren]

It's getting to the point where i can't use https://redirect.invidious.io, bcs it keeps loading this cloudflare-gated provider that blocks hardened web browsers and applications -> Requesting it to be removed.

Problematic providers:

1. https://invidious.kavin.rocks
2. https://invidious-us.kavin.rocks

[ghost]

This issue is probably supposed to be in https://github.com/iv-org/invidious-redirect (maybe transfer or close?)

bcs it keeps loading this cloudflare-gated provider

It doesn't seem to load anything other than some javascript, all it generally does is display a list of invidious instance urls. If your talking about it being listed, you can just select another instance.

that blocks hardened web browsers and applications

Seems to work fine on my hardened firefox setup (arkenfox), maybe a good alternative to this is display if an instance has DDoS protection like #17?

[SamantazFox]

@arche-dev there is an automatic redirect inside invidious itself (which uses the same instances as the redirect), hence why the bug being reported here.

We're planning on a rewrite of the instances list/API so better filtering can be done (e.g: no CF, no modified styles, etc...).

[arrowgent]

explain your hardened browser config

kavin.rocks works fine and is a great instance resource for multiple services

[Kreyren]

explain your hardened browser config -- @arrowgent (https://github.com/iv-org/invidious/issues/2747#issuecomment-1001629070)

Unable due to the threat model: Disclosing how exactly my browser works would make me fingerprintable due to the issues associated with randomization of a fingerprint (it's more likely to be unique in comparison to tor browser as now all values that are reported by the browser are known + the threat of AI learning human behavior).

To help with reproduction: From my experiments If cloudflare ("CF") can't fingerprint you (by assigning Cloudflare Ray ID) then their "DDoS protection" won't let you use the website.
This ID is reported in the footer of the website so if you can get a browser that is capable of showing a different ID on page refresh then you should be able to reproduce the issue.

In terms of CF it seems to be a combination of:

1. Link tracking (adding metadata in the URL bar)
2. WebGL
3. Javascript
4. Hardware fingerprinting
5. onion-routing
6. Canvas data

[Quix0r]

2. redirects to https://piped.kavin.rocks so that's an other issue (and many other redirect-to instances have, too) as it is abandoned.