pfrazee

body {
  --light-gray: #f7f7fc;

  font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen, Ubuntu, Cantarell, 'Open Sans', 'Helvetica Neue', sans-serif;
  margin: 0;
  display: grid;
  grid-gap: 10px;
  grid-template-columns: 300px 1fr;
  grid-template-rows: 100px 1fr;
  min-height: 100vh;

pfrazee

const archive = await DatArchive.load('someurl')

var fooExt = archive.extension('foo')

// listen to 'foo' messages from all peers
fooExt.addEventListener('message', ({detail}) => {
 const {message, peer} = detail

  // send to one peer:
  await peer.extension('bar').send('Hello World')

pfrazee

For the theme, I'm leaning toward using a template file.

• The "theme dat" has been mounted to the site's /theme directory.
• User visits /index.html on the site
  • The /theme/template.html file is loaded.
  • The /index.html file is loaded.
• Output is constructed:
  • The template <!-- TEMPLATE-CONTENT --> string gets replaced with the content of /index.html
  • The resulting string is served.

pfrazee

DNS handling in beaker

Dat site "Primary URL" (pURL)

Within Beaker, all Dat sites have a "Primary URL" (pURL). This is dat://{key} by default. Dat sites can assign multiple DNS short names, but the pURL will only be changed to a DNS shortname if the site's dat.json assigns a "domain" value. This value will be confirmed against the DNS record.

Therefore the "Primary URL" can be visualized as:

var hostname = key

pfrazee

Dat Simple Directories (DSD)

The premise of Dat Simple Directories (DSD) is that organizations such as companies, schools, agencies, and communities can act as the backbone of global identity.

Organizations will typically have the following desirable properties:

• The resources to deploy websites with DNS and SSL
• A need to maintain and publish their membership
• An interest in maintaining their reputation

pfrazee

Beaker/Dat code modules proposal

Like node and other platforms, Beaker will need a way to share modules of code and other assets. The Web's ES Modules give us a lot of the tooling for importing and exporting javascript, but we still need solutions for publishing, versioning, and "installing" dependencies.

This is a proposal to use Dat archives and ES Modules in Beaker to solve code-sharing.

Overview

"Module" dat archives have a folder structure that includes the current development code in /dev and any frozen versions in /v. A trivial example of that folder structure:

pfrazee

Four new proposed schemas for Unwalled.Garden

This week I created PRs for four new unwalled.garden schemas. The are:

• Actions
• Discussions
• Relationships
• Votes

Of these, I'm 99% sure that Discussions and Votes should land. I think Actions and Relationships could be fun additions, but I'm open to disagreements about them.

pfrazee

Blue setup / build process

Create a new directory, let's say ~/blue.

mkdir blue
cd blue

Clone the following repos:

pfrazee

const path = require('path')
const fs = require('fs').promises
const MarkdownIt = require('./vendor/markdown-it.min')
const hljs = require('highlight.js')

const md = MarkdownIt({
  html: true, // Enable HTML tags in source
  xhtmlOut: false, // Use '/' to close single tags (<br />)
  breaks: true, // Convert '\n' in paragraphs into <br>
  langPrefix: 'language-', // CSS language prefix for fenced blocks

pfrazee

User drive's folder structure:

/data/         - json records
/website/      - html/css/js for visiting them as a site
/drives/       - published drives
/dat.json      - metadata
/thumb.jpg     - avatar
/favicon.ico   - icon
/cover.jpg     - cover photo in social cards/profile page