UI Use Cases
From Entuura
Here is a list of use cases, showing the ways that users interact with the Entuura system.
Contents |
A home page
A user opens a web browser configured with a certain URL as home page and sees a view of those features of the installation important to him in his role.
Features "beyond" his role, but of interest to him should be discoverable by hints the UI offers to him. For example, a data entry clerk should be able to discover a blog article ranking his site's health metrics.
User login and roles, and unauthenticated users
The system is usable and provides appropriate information to an unauthenticated user. Data published in this way is attributed to the site as a whole via a reserved pseudo-username (i.e. None@$node.$community).
Users can login and then interactions they have with the system are attributed to their own name. Users identify themselves with passwords, but passwords can be turned off if that's more appropriate for a site's context. Usernames are as close to human readable as possible, and support Unicode character sets. If there is an underlying username encoding scheme, it is invisible in the UI.
Internally to the system, a cryptographic key represents a user. User passwords decrypt the key. There is no conventional password store -- setting us up for a future where users are identified to the system by a key which is held outside the system.
Roaming Users
Eventually we expect that all users inside of a community to be able to identify themselves at any node in the community in order to get some services, for example visitors access to the Internet.
This user case opens difficult, but solvable, questions of distributed directories, key custodianship, etc. The UI should look forward to the day these questions are solved and roaming works.
Roles
A role informs an application on how to behave, and how much to trust a user.
One or more roles can be attached to each user.
Captive Login
A user who joins the network has a chance to see the Entuura UI without needing any additional configuration.
With one click, they can avoid being interrupted by the UI until the end of the session. The UI remains available in another window.
