Beaker Browser Specs
Every specification has its own file. To discuss the content of a spec, open issues and PRs on this repo.
Getting started
Looking to learn about how Beaker works? Start here:
- User data and identity
- Beaker user identities. APIs and UI flows for user identities.
- Beaker user filesystem. The filesystem for users' personal information.
- Filesystem APIs
- Object-store folders. Managed folders which help applications share data.
- Manifest files and metadata
Directory
Phase 0 - Proposals Under Consideration
| Spec | Description | Last Updated |
|---|---|---|
unwalled.garden |
Not yet written. A collection of schemas used by Beaker. | |
DatArchive API |
Not yet written. Refer to the documentation for now. | |
PeerSockets API |
Not yet written. Refer to the PR for now. | |
DatPubkeyFile API |
Not yet written. Refer to this gist for now. |
Phase 1 - Accepted Drafts
| Spec | Description | Last Updated |
|---|---|---|
| Beaker user filesystem | The filesystem for users' personal information. | Nov 6, 2018 |
| Beaker user identities | APIs and UI flows for user identities. | Nov 7, 2018 |
| Dat types | Standard dat "type" values and their effects in Beaker. | Nov 6, 2018 |
| Object-store folders | Managed folders which help applications share data. | Nov 6, 2018 |
Phase 2 - Stable
| Spec | Description | Last Updated |
|---|---|---|
| dat.json | The dat.json standard manifest file. Used to describe a dat. | April 20, 2018 |
Status badges
