[New instance] invidious.f5.si

[Netscape7]

URL

https://invidious.f5.si

Mandatory checks

• Instance has a domain name
• Instance is served over HTTPS
• Statistics (/api/v1/stats) are enabled
• Instance is properly configured (including the mandatory post install configuration)
• Instance has an automatic hourly restart setup of Invidious
• If dash, proxy + download is enabled (default settings), the instance has unlimited traffic/bandwidth or close to unlimited (100TB minimum)
• Instance is not running any kind of analytics, including external scripts of any kind
• If using Cloudflare or any other DDoS protection service, settings are configured to allow uptime monitoring. Cloudflare users can consult this guide

Maintainer chart

• Ensure that my instance is up to date (less than one month old)
• Ensure a proper uptime of my instance (around 90%)

Rules for public instances

• I agree to follow the rules for public instances

Host country

Japan

Man in the Middle

Cloudflare

Source code URL

No response

Your matrix username

udukikousei

Additional information

No response

[github-actions]

Hello! Your instance has been added to our monitoring system: https://updown.io/g2me
You need to wait 30 days before we add your instance, this is to evaluate that your instance will keep a good uptime for one month.

Make sure you double checked all the mandatory checks or this will slow down the process of adding your instance!

Please consult these two important tutorials:

• Escaping the YouTube block (403 errors in playback): https://docs.invidious.io/ipv6-rotator/

• Improving the performance and the stability of your public instance: https://docs.invidious.io/improve-public-instance/

It is highly recommended to follow these tutorials because it will allow the instance to stay stable and performant over the long term.

[unixfox]

Hello, since October a lot has happened. YouTube is cracking down heavily on 3rd party softwares using their unofficial API like Invidious.

This mean that once your instance will be added to the public list, there is a very high chance it will stop working after a day. It's possible that your instance may survive this blockage if you are running it on a residential IP address because YouTube seems to be more kind towards residential IPs. We don't exactly know at what limit they consider banning the IP address.

Currently, the counter-measures employed by the existing instances are rotating the IP address every hour, as of right now there is no guidance regarding that so you will need the knowledge in this field to keep your instance running.

Do you still want to run a public instance?

[Netscape7]

Yes. I will continue to run a public Invidious instance.

I am using a residential IP address to host Invidious, so it is unlikely that the instance will be blocked. Even if it is blocked, I can easily circumvent the blockage by rebooting my router and generating a po_token and visitor_data ID.

My ISP also supports IPv6, so I can use ipv6-rotator to circumvent the blockage.

DMCA requests probably won't be an issue. (Japanese ISPs probably don't know much about it.)

Translated by Google Translate

[unixfox]

OK.

ipv6 rotator does not work anymore, google block all the entire ipv6 range.

If you have to reboot your router every hour, I'm not sure if your ISP will like that.

[Netscape7]

I've never tried changing my IP address every hour, but it's not prohibited so my ISP probably won't do anything about it.
But if I get any warning about IP address changes, I might reduce the frequency. Will that affect my public instance listings?

[unixfox]

Well it's quite simple, if your instance works, we keep it on the list. If your instance stop working, we remove it.

Up to you to manage it so that it keeps working. I'm only warning you on the possible outcomes.