Would this act as a bool value in the core lib-p2p node’s configuration? As in it could be add to the peerDiscovery array of the LibP2P node instance? Offering your node as an agnostic seeder for peers looking for other app specific peers?
Yes, you’ll be able to just pass it into peerDiscovery with additional configuration as needed. The relay server will do this, so we’ll be able to point to that configuration as a sample.
could you then create a private network within that subscribed game? ie.
It wont be private at the network level, but you could configure the application to support this. If you join a namespaced pubsub discovery network for your application, you could discover everyone actively online who is also running the app. The next thing is connecting to the peers that are in the same campaign(s) as you. This could potentially be done via pubsub, by subscribing to a campaigns topic, however every peer in pubsub would learn about the campaign through querying (not necessarily a bad thing). While peers could know about your campaign, you could add application logic to include a secret key to “join”. So when a peer connects to you and wants to join your campaign, they would need to send you the secret key for the campaign in order to get the data. When you start a campaign with your friends you could send them the campaign ID and secret key. They could find you on the public network (libp2p supported) and then you’d get the privacy of the shared secret (application logic) to actually access the data.