documentation/docs/instances.md
Émilien Devos (perso) da5af47a87
add multiples instances
closes #340
closes #330
closes #352
2023-04-04 13:08:31 +00:00

7.3 KiB

Invidious Instances

Uptime History provided by Uptimerobot

Instances API

Warning: Any public instance that isn't in this list is considered untrustworthy. Use them at your own risk.

List of public Invidious Instances (sorted from oldest to newest):

Tor Onion Services:

I2P Eepsites:

Rules to have your instance in this list:

  1. Instances MUST have been up for at least a month before it can be added to this list.
  2. Instances MUST have been updated in the last month. An instance that hasn't been updated in the last month is considered unmaintained and is removed from the list.
  3. Instances MUST have statistics (/api/v1/stats) enabled (statistics_enabled:true in the configuration file).
  4. Instances MUST have an uptime of at least 90% (according to uptime.invidious.io).
  5. Instances MUST be served via domain name.
  6. Instances MUST be served via HTTPS (or/and onion).
  7. Instances using any DDoS Protection / MITM MUST be marked as such (eg: Cloudflare, DDoS-Guard...).
  8. Instances using any type of anti-bot protection MUST be marked as such.
  9. Instances MUST NOT use any type of analytics.
  10. Any system whose goal is to modify the content served to the user (i.e web server HTML rewrite) is considered the same as modifying the source code.
  11. Instances running a modified source code:
    • MUST respect the AGPL by publishing their source code and stating their changes before they are added to the list
    • MUST publish any later modification in a timely manner
    • MUST contain a link to both the modified and original source code of Invidious in the footer.
  12. Instances MUST NOT serve ads (sponsorship links in the banner are considered ads) NOR promote products.

NOTE: We reserve the right to decline any instance from being added to the list, and to remove or ban any instance that repeatedly breaks the aforementioned rules.