-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[New instance] lekker.gay #618
Comments
Hello! Your instance has been added to our monitoring system: https://updown.io/cjxs 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:
It is highly recommended to follow these tutorials because it will allow the instance to stay stable and performant over the long term. |
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? |
Thanks for the message. I'm currently running on a residential IP, with the IPv6 rotator running twice per day. Thank you for all your efforts for this awesome project. |
URL
https://lekker.gay
Mandatory checks
/api/v1/stats
) are enabledMaintainer chart
Rules for public instances
Host country
The Netherlands
Man in the Middle
CloudFlare
Source code URL
No response
Your matrix username
@karel:lekker.gay
Additional information
No response
The text was updated successfully, but these errors were encountered: