Many dead invidious instances

[vinoff]

Here are some dead instances:

https://invidious.silkky.cloud/

https://vid.mint.lgbt/

https://invidiou.site

https://invidious.048596.xyz

https://invidious.tinfoil-hat.net

https://inv.skyn3t.in

[vinoff]

https://rtbstream.com

[vinoff]

invidious.xyz/

[vinoff]

https://invidious.himiko.cloud

[m77e4t]

I recommend using https://invidious.kavin.rocks and https://yewtu.be. Both of them have high uptime and rarely go down.

[mooreye]

Wouldn't it be better to auto-fetch current instances from things like https://redirect.invidious.io/ or https://github.com/zedeus/nitter/wiki/Instances or https://searx.space/ instead of maintaining a hardcoded list? It should of course be possible to disable to prevent unwanted calls to these websites if one wishes.

[aaronkurz]

I could work on this ticket if that is okay? 😄

[m77e4t]

Similar open issues https://github.com/SimonBrazell/privacy-redirect/issues/171 https://github.com/SimonBrazell/privacy-redirect/issues/48 https://github.com/SimonBrazell/privacy-redirect/issues/101 and others, where the community is unable to solve it for 2-3 years.

A guy was asking $20 to solve the issue :) https://github.com/SimonBrazell/privacy-redirect/issues/171#issuecomment-825743559

If someone is actually able to solve it (in a privacy preserving manner) it will be pretty good.

[aaronkurz]

I think for invidious, we could just poll the HTTP endpoint https://api.invidious.io/instances.json?sort_by=type,health and randomize for the top instances. It would not be a very big performance impact imho. (and if that api turns out to be inaccurate, pinging each item on the list and excluding the instances returning anything else than 2xx status codes would also be feasible)

[mfed3]

https://invidious.himiko.cloud

This one actually redirects to a domain that has been taken over by a spam site riddled with trackers. Highly recommend this issue gets fixed and be sure to remove this entry.