This Web site is dedicated to providing information about an abstract peer-to-peer operating system called Kueea System.
Kueea System is divided into components called modules. Modules are meant to be narrow in scope and be developed so that the module eventually reaches a 'final' state, is frozen and never updated again. For example, one module defines methods for computing SHA-2 hash sums. It does not define anything else.
Modules are black boxes that communicate via their pre-defined interfaces. Each module is identified by a globally unique identifier, which acts as its namespace, under which objects and methods are defined. Modules have an associated revision number, which may only increase. Higher revisions are always backward compatible with previous revisions.
Devices load into memory and execute module implementations. It is expected that there will be different implementations available, some published as free software, others requiring payment to use. The primary goal of this Web site is to gather module definitions in one place and provide references to their implementations.
In Kueea System, data and applications are separate layers. Program behaviour is defined by modules, whereas data is referenced in a way, which enables resources to be individually addressed in the global scope. The tree structure of filesystems in abandonded in favour of a graph, within which nodes are named using globally unique names. Effectively, devices conforming to the system specifications may reference data stored on each such device, creating a data network layer. What differs from the usual cloud system is that these devices are not under control of one entity and are therefore untrusted by default.
At the core of device-level networks lie policy definitions. Only those, who apply the same policies regarding system operation, such as data access policies and user authentication and authorization, may securely communicate with each other because their trust anchors match. The system is designed in way so that peers verify each other in order to test conformance with the agreed-upon policies. In the event a malicious peer is detected, other peers are informed of this and said malicious peer is banned from the network for bad behaviour.
One of Kueea System's goals is to establish globally unique user identities, so that behaviour of users is reflected across the whole Internet, not just within one particular service. Yes, every peer within Kueea System is expected to track user behaviour. Before you start panicking, please understand that in a situation when you talk with another in person, you are effectively being tracked, because the other person is listening to you and is watching your gestures. What matters is not the fact of being tracked, it is how and for what purpose tracking data is used and collected. One user may be rejected access because it has been marked as a troll, another may be given some benefits because of its good reputation.