Blog

Dat uses an append-only feed that’s inspired by Certificate Transparency to create auditable change logs in file archives. We use this to deliver Web applications securely in Beaker.

We love services like GitHub, Codepen, and Glitch, for providing tools to share, duplicate, and remix other people’s projects. What if instead of being part of a one-off service, these tools were a core feature of the Web platform?

In Beaker 0.7.2, we made policy updates that enable an application model we call “Self-mutating websites.” In this post, I’ll explain what they are and how to get the most out of them.

The spirit of openness has been baked into the Web since its formation. The Web was built to share documents written in plain text that could be downloaded and viewed transparently.

The latest release fixes a set of bugs found in 0.7 and adds a new “Swarm debugger” to help users diagnose peer connectivity issues.

We’re big fans of Markdown, so we’ve built in support for Markdown formatting to Beaker.

The latest release fixes a set of bugs found in 0.7 and adds a new “Swarm debugger” to help users diagnose peer connectivity issues.

I’m happy to announce that Beaker 0.7 is ready to download. You can read the full set of updates in the release notes. This was a big update with a lot of amazing protocol work by the Dat project.

A few new updates to Beaker. You can now give DNS sites a shortname. You can use the new dathttpd web server to host your sites from the cloud, and take advantage of this new feature. (Read the spec here.)

A big part of this release was about improving the UX. We’re thinking very specifically about how we want Beaker, as a product, to work. We took inspiration from a lot of different products, including CodePen, GitHub, and even iTunes.

The other major half of this release was making fixes to the Dat protocol. We’ve improved our debugging techniques, and found some key issues that we’ve patched.