Title, currently the instances-api pulls the Instances list from the markdown file using regex, but this makes it more complex to make more information available to the instances-api for other types of instances like Invidious instances running on the Yggdrasil network but using a clearnet URL (like https://inv-ygg.nadeko.net/, which resolves to 202:415c:2061:a9c0:9dbc:b95d:66ec:1347, a Yggdrasil IP address). Currently the logic to detect if an Instance is hosted in Tor or I2P is using their TLD, .onion Invidious instances will appear as hosted in the Tor network, and .i2p ones in the I2P network, but this is not the case for instances hosted in Yggdrasil.
So I was thinking about adding some sort of instances.json file to the https://github.com/iv-org/documentation repository so it can read structured information for the instances instead of relying on reading the markdown file and extracting the information from there, so we can mark Yggdrasil instances hosted using "clearnet" TLDs.
Title, currently the instances-api pulls the Instances list from the markdown file using regex, but this makes it more complex to make more information available to the instances-api for other types of instances like Invidious instances running on the Yggdrasil network but using a clearnet URL (like https://inv-ygg.nadeko.net/, which resolves to 202:415c:2061:a9c0:9dbc:b95d:66ec:1347, a Yggdrasil IP address). Currently the logic to detect if an Instance is hosted in Tor or I2P is using their TLD,
.onionInvidious instances will appear as hosted in the Tor network, and.i2pones in the I2P network, but this is not the case for instances hosted in Yggdrasil.So I was thinking about adding some sort of
instances.jsonfile to the https://github.com/iv-org/documentation repository so it can read structured information for the instances instead of relying on reading the markdown file and extracting the information from there, so we can mark Yggdrasil instances hosted using "clearnet" TLDs.