Proposal: Support dat shortnames via TLS, and automate HTTPS->Dat discovery

[Paul Frazee]

We're working on a bridge between HTTPS and Dat. The goal is to have a nice nix tool like

dat-http {dat-url} --port 443 --cert {pemfile} --key {pemfile}

which would dual-host a site over Dat and HTTPS. Beaker would then be able to load dat://yoursite.com, and would prompt visitors of https://yoursite.com to redirect to dat://yoursite.com.

An example of this is https://www.datprotocol.com/, which is also hosted at dat://ff34725120b2f3c5bd5028e4f61d14a45a22af48a7b12126d5d588becde88a93/. We'd like it to serve at dat://www.datprotocol.com too, and for the https visitors to switch to the dat version.

To support this, we need a protocol for securely mapping DNS names to full Dat URLs. Please submit your comments to this thread, or in the GitHub issue linked below.

Proposal: https://github.com/beakerbrowser/beaker/wiki/Authenticated-Dat-URLs-and-HTTPS-to-Dat-Discovery

Discussion: https://github.com/beakerbrowser/beaker/issues/227

-prf