Thanks for the links, and sorry, I’m slow reading the forum.
Since the first versions of g1nkgo, it scans the peers (in v1) and selected the best nodes, tracking errors and their latency. For scanning the nodes, it uses some hardcoded v1 nodes in the code configuration. The thing is that this starting point, sometimes failed (because well know working nodes, sometimes also fail). This is why I suggested having a Ǧinspecte · json call to try to find other working nodes.
I see now that in v2 we can scan it too (I started to use it in g1nkgo, and it tries to find some new nodes), and we have a gitlab list (I have to add it too), but, I’m proposing to have several ways to retrieve a boot start list of nodes, not only the hardcoded + gitlab + network scan.
I used to visit Ǧinspecte when things are not working properly, so this is why I suggest using it also by the apps to retrieve an extra list of nodes.