confidential-storage
confidential-storage copied to clipboard
decentralized-identity
Paradigm shift to shift from client server to content providers/consumers
I will make a PR to wordsmith the architecture ... but just as a general paradigm to level-set the brave new world.
“Client–server model is a distributed application structure that partitions tasks or workloads between the providers of a resource or service, called servers, and service requesters, called clients.[1] “
- https://en.wikipedia.org/wiki/Client%E2%80%93server_model
I think we should add some informative text before we start using the term client / server to note that its not just about big centralized servers... I do find the concept of client-server very helpful as a developer...
I use https://github.com/ipfs/js-ipfs/tree/master/packages/ipfs-http-client all the time.
I do think the terms client and server are very helpful, especially when contextualized properly...
Consumers is too vague for me. Is the requesting party (the one with credentials or claims) the consumer or is the software they're using to connect to the provider the consumer?
In OAuth terminology the role of the RqP is separate from the role of their Client. The client is typically controlled by the employer of the RqP and may have software statements or credentails of its own. Zero-trust security architecture seems to be trying to rationalize this RqP vs. Client distinction and that's a good thing.
