fa3722a38f
We remove the local<->eauth switching tabs entirely. The only way to see the eauth login page is if the url contains an "eauth" query parameter. (Entering the local ship name into the eauth form still brings you to the normal login screen.) The "proceed as guest" blurp no longer shows the guest identity, and we clarify the language to indicate that it is not guaranteed to result in access to content. Both of those changes help simplify the look and feel of the login page. Various users had complained that it was confusing, given that logging into your own ship is still the common case, and not everyone knows what "euauth" is. For applications redirecting to the login page, it is still recommended to add the ?eauth GET parameter if non-local sessions are supported. For applications that don't it should now be more obvious that logging in through eauth won't do anything (since it's not presented as an option). We also remove some debugging prints that somehow remained in the javascript. |
||
|---|---|---|
| .github | ||
| bin | ||
| doc/spec | ||
| extras | ||
| nix | ||
| pkg | ||
| sh | ||
| tests | ||
| .gitattributes | ||
| .gitignore | ||
| .ignore | ||
| .mailmap | ||
| .stylish-haskell.yaml | ||
| CONTRIBUTING.md | ||
| default.nix | ||
| flake.lock | ||
| flake.nix | ||
| LICENSE.txt | ||
| MAINTAINERS.md | ||
| Makefile | ||
| README.md | ||
| shell.nix | ||
| test-desk.bill | ||
| vere-version | ||
Urbit
Urbit is a personal server stack built from scratch. It has an identity layer (Azimuth), virtual machine (Vere), and operating system (Arvo).
A running Urbit "ship" is designed to operate with other ships peer-to-peer. Urbit is a general-purpose, peer-to-peer computer and network.
This repository contains the Arvo Kernel
For the Runtime, see Vere. For more on the identity layer, see Azimuth. To manage your Urbit identity, use Bridge.
Install
To install and run Urbit, please follow the instructions at urbit.org/getting-started. You'll be on the live network in a few minutes.
Contributing
Contributions of any form are more than welcome! Please take a look at our contributing guidelines for details on our git practices, coding styles, and how we manage issues.
You might also be interested in joining the urbit-dev mailing list.
Release
For details about our release process, see the maintainers guidelines