I’m trying the Beaker browser now. Sez the site, "Beaker is a peer-to-peer browser with tools to create and host websites. Don't just browse the Web, build it."

Interesting sign of our times: it’s ready on Linux and Mac, and “coming soon” to Windows.

The video on the Beaker index page (above) is a good intro, and then leads to Jeremy Ruston’s video of TiddlyWiki+Beaker.

(I haven’t seen Jeremy in years, but we got a lot of hang time when we were both working for JP Rangaswami at BT.

Key to Beaker is dat.

More in Github about dat-http. Specifics:

An HTTP transport/storage provider for Dat, allowing replication of Dats over normal HTTP connections from flat files on the server. Currently only supports read operations, write operations coming in the future (open an issue if you need this).

The entire .dat folder must be available on the server for this to work. Point this at the root url where the .dat folder is and you can use this to do replication.

This is implemented as a storage provider, conforming to the https://www.npmjs.com/package/abstract-random-accessAPI. That may seem counterintuitive, as this provides a networkworking transport but implements a storage provider API. However, in Dat you can wrap a storage provider in a Hyperdrive instance to turn it into a network transport.

I’ve added the Beaker browser to the “privacy protection” section of the VRM developments roster.

This whole thing needs a big re-arrange. If you want to help, talk to me. Thanks.