Federated 3rd party hosting and mission statement

[SomajitDey]

• Authentication: Registered with the Securelay foundation / authority
• Incentive: social economy => digitally signed community-service/contribution certificate with verified socials to be used in CV/resume, portfolio or as bragging rights in social media
• Quality Control: Random automated audits; ban and certificate revocation on failing QoS standards
• Allowed: Random downtimes and bandwidth/request caps. Incentive certificate includes uptime/SLA and rate of requests served to discourage low availability/capacity
• Coordination: stateless accounts are bound to the server that issued the private-public key pair. But any server can redirect requests to that original server, if up, after identifying it using an internal pubsub gossip maintained by the active servers. If the original server is down, however, the current server can still serve public requests (but not private), because it can still retrieve the cloud backends/webhooks from the original server's always on CDN. Stateful accounts stored/retrieved and authenticated using Git-NS can be used with any server
• Comparison to IPFS: IPFS -DHT nodes and -Relay providers have no official/well-recognized incentives. Also, it is naive to expect that every user will operate their own node when there are so many offerings (including budget/freemium ones) for managed cloud-backends
• Mission statement: Let user's private data live in their chosen infra and public data in global CDNs. Let users stream to and from the world using their own bandwidth and their chosen relay provider, if NAT traversal or IP-anonymity is needed. Let only a few people who self-host out of pride, ambition, hobby or need (portfolio/resume asset) act as managers deciding who corresponds with whom according to a standard protocol enforced and quality controlled strictly by a central authority