[1] Beaker | Dat files protocol () https://beakerbrowser.com/docs/inside-beaker/

In Beaker, a Dat archive acts as a website. The public key serves a similar purpose as an IP address in HTTP/S URLs; it is the domain which identifies the site. Dat URLs are formed as dat://{publickey}/{path…}, where publickey is a 64-character, hex-encoded string.

[2] Beaker | Dat files protocol () https://beakerbrowser.com/docs/inside-beaker/

Dat’s internal logs enable history archival and versioned reads. Using the log sequence numbers, it is possible to create versioned URLs such as dat://{pubkey}+{version}/{path…}.

[3] Authenticated Dat URLs and HTTPS to Dat Discovery · beakerbrowser/beaker Wiki () https://github.com/beakerbrowser/beaker/wiki/Authenticated-Dat-URLs-and-HTTPS-to-Dat-Discovery

Beaker needs a mechanism by which users can securely deploy a site at a domain, eg dat://beakerbrowser.com. Ideally, this mechanism will allow discovery and automatic redirection; for instance, if the user browses to https://beakerbrowser.com, they should be prompted to redirect to dat://beakerbrowser.com.

[4] beakerbrowser/dathttpd: A Web server for Dat and HTTPS, with zero-config TLS. () https://github.com/beakerbrowser/dathttpd

Dat sites are hosted at public keys, which are the equivalent of IP addresses in the P2P network. The pubkeys are ugly, though! Wouldn't it be nice if your dats could have nice DNS shortnames, and also rehost over HTTPS for people still on legacy browsers?

dathttpd is for you!

[5] beakerbrowser/beaker: peer-to-peer web browser with support for dat:// () https://github.com/beakerbrowser/beaker

[6] fileset_ho376wmdanckpp66iwfs7g22ne | fatcat! () https://fatcat.wiki/fileset/ho376wmdanckpp66iwfs7g22ne

<tr><td class="two wide right aligned">dweb

<td class="eight wide"><small><code><a href="dat://77e94744aa5f967e6ed7e3990bfc29f141dbf2c0fff572eb1212b3bd706882f4/files/">

dat://77e94744aa5f967e6ed7e3990bfc29f141dbf2c0fff572eb1212b3bd706882f4/files/

</a></code></small>