Stealth: Peerer Server Middleware

[cookiengineer]

The Compeer implementation is now almost ready. What's missing is a dedicated Review for its featureset and the integration of peers to the Settings in the Browser Profile and the stealth.peers[] Array that contains active Peer connections.

• Services: Implement a better Peer Settings structure.
• Compeer: Implement this.services.peer API integration that creates a Peer (if it doesn't exist) or updates a Peer (if it exists) Setting.
• Implement stealth/server/Compeer Review.
• Fix/Update stealth/server/service/Peer Review.

let peer_setting = {
    domain: 'hostname' || 'username.tholian.local',
    peer: {
        connection: 'mobile', // internet.connection setting
        certificate: 'hash_value' || null, // hash of peer certificate for cert pinning. No certificate means no secure connection
        version: '2021:X0' // Stealth.VERSION to reflect API compatibility
    }
};

[cookiengineer]

The Peerer should manage the task of local and global peer discovery, and add the responses accordingly to the this.stealth.settings.peers[] array (and settings.hosts[]).

In order to clean up the Peer Service, the proxy() method has been removed, and instead the SOCKS and HTTPS Proxy should now be used to achieve the same effect of relaying network traffic. However, the following use cases have not been solved yet:

• receive() should save ServiceDiscoveryResponses into settings.peers[]
• resolve() DNS requests to other domains via known local Peers on port 65432, use a Ronin mechanism to select peers at random, if unsuccessful repeat max 3 times.
• resolve() local Peer domains (*.tholian.local) via settings.peers[] and settings.hosts[].