iv-org-mirror/documentation
1
0
Fork 0
mirror of https://gitea.invidious.io/iv-org/documentation.git synced 2024-08-15 00:53:34 +00:00
Code Issues Projects Releases Packages Wiki Activity

Remove duplicate prerequisites on inst. add secti.

Browse source 
Update templates in instances.yaml
This commit is contained in:
syeopite 2021-05-30 06:27:34 -07:00
parent 4fc42649f9
commit 78929a0b7a
No known key found for this signature in database
GPG key ID: 6FA616E5A5294A82
1 changed files with 11 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

18
instances.yaml
View file

@ -3,7 +3,7 @@ adding_instance:
- 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. - 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.
- Instances must have statistics (/api/v1/stats) enabled (statistics_enabled:true in the configuration file) - Instances must have statistics (/api/v1/stats) enabled (statistics_enabled:true in the configuration file)
- Instances must be served via domain name. - Instances must be served via domain name.
- Instances must be served via domain name. - Instances must be served via HTTPS.
- Instances using any DDoS Protection / MITM are marked as such. - Instances using any DDoS Protection / MITM are marked as such.
- Instances using any type of anti-bot protection are marked as such. - Instances using any type of anti-bot protection are marked as such.
- "Instances using any type of analytics are marked as such, must be GDPR compliant (if it's usable in the EU), must be CCPA compliant (if it's usable in California), and must respect the AGPL by explaining their changes and by publishing their source code. In short: instances shouldn't run analytics, because it's not worth it." - "Instances using any type of analytics are marked as such, must be GDPR compliant (if it's usable in the EU), must be CCPA compliant (if it's usable in California), and must respect the AGPL by explaining their changes and by publishing their source code. In short: instances shouldn't run analytics, because it's not worth it."
@ -17,13 +17,17 @@ adding_instance:
instances: instances:
https: https:
# Template instance # Template instance
# - url: example.com # - url: https://example.com
# country: # country:
# flag: 🇫🇮 # flag: 🇫🇮
# name: Finland # name: Finland
# status_url: status.example.com # status:
# privacy_policy: privacy.example.com # url: https://status.example.com
# ddos_mitm_protection: Cloudflare # display_content: https://status-image.example.com
# display_content_is_image: True
# display_content_image_fallback: uptime status
# privacy_policy: example.com/privacy
# ddos_mitm_protection: null
# owner: https://github.com/example # owner: https://github.com/example
# modified: # modified:
# is_modified: False # is_modified: False
@ -235,8 +239,8 @@ instances:
# country: # country:
# flag: 🇺🇸 # flag: 🇺🇸
# name: USA # name: USA
# associated_clearnet_instance: example.com # associated_clearnet_instance: https://example.com
# privacy_policy: privacy.example.com # privacy_policy: https://privacy.example.com
# owner: https://github.com/example # owner: https://github.com/example
# modified: # modified:
# is_modified: False # is_modified: False