The public nodes are randomized each time they are loaded, so there is no difference or any meaning attached to one particular node.
The public nodes are currently hard-coded. It is possible to setup a separate repo specifically for the purpose for maintaining a public node database. Something similar as to what ledger does with the ledger-app-database.
PR’s are made to add or remove app registrations from the list, which is basically one big json file.
In our case the repo would serve as a public node database which can be used by various applications. bc I believe syrius isn’t the only application in need of this list.
Once the repo is setup, syrius can use the repo from within the build workflow. This would still require a build to include the latest version, but it does separate the list from the syrius repo. Making it available for other applications to use and in the same time have some standardized way of maintaining it.