-
Notifications
You must be signed in to change notification settings - Fork 157
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
Rewrite the public instances list #74
base: master
Are you sure you want to change the base?
Rewrite the public instances list #74
Conversation
https://invidious.048596.xyz is ran by @tenpura-shrimp See #6 |
Should something like "Instances using a modified source code, are required to publish their source code before they can be added to the list, and must timely publish any later modification in a timely manner." be added to prevent another #72 from happening? |
Done, thanks :) |
I think we should add an uptime requirement. Any instance that is down most of the time should not be added to the official list imo. |
This is a good idea, should how much should we require? 75%? |
At the very least 90% because it's still like almost 3 days per month of downtime: |
Yeah, you're right. 90% is the way to go I guess. |
This PR can get merged soon. I've finished the parser rewrite for the instances-api a few days ago. See iv-org/instances-api#30 |
Owner for https://notyoutube.org is wrong. The actual owner is dejalavidavolar. See #58. But due to #82 it should be removed |
Rendered version: https://github.com/TheFrenchGhosty/documentation/blob/instances-list-rewrite/Public-Instances.md
This PR is a rewrite of the public instances list from scratch.
It is "incomplete" in the sense that it's missing the link to some privacy policies, and the owners of the Tor onion, but it's enough for https://github.com/iv-org/instances-api to be adapted to work with it.
It mustn't be merged before https://github.com/iv-org/instances-api is ready to support it. (@syeopite seems to plan to rewrite its parser)
Took me around to do ~2 hours, it was a lot more time consuming that I expected.
Note:
The wording of some categories have to be discussed (mainly "DDos Protection / MITM").