~?~

~?~

~?~

Paul Frazee github twitter beakerbrowser.com I work on a peer-to-peer browser called Beaker . I live in Austin TX. this is still a secret! We run a public-peer service called <a href="https://hashbase.io">Hashbase</a>. RSS Feed <-- home December 22, 2016. @pfrazee One of the on-going questions of decentralized tech is, how will it scale? Which is another way of saying, is it viable? The Web has always been about scale. If we’re not able to produce Web-scale applications, then it’s time to pack up and go home. Addressing this for the P2P Web stack ( Beaker and Dat ) is interesting both as a technical discussion, and as an exploration of viability. Start with: What is the P2P Web? Dat sites are mutable file archives. They are syncronized in active swarms, and each of them maintains a changelog. When there’s a write, an entry is added with the updated...

<-- home February 22, 2017. @pfrazee Configure the variables in this post $YOUR_DNS $YOUR_DAT $YOUR_EMAIL As of Beaker Browser 0.6.1 , you can visit Dat sites using DNS shortnames: This is accomplished with DNS-over-HTTPS, and made simple with DatHTTPD . DatHTTPD serves Web sites over HTTPS and Dat with automatic TLS certificates. DNS shortnames for Dat were not possible until Beaker 0.6.1 . We needed a secure way to transmit a DNS mapping for non-HTTPS sites. Originally we used DNS TXT records, but the lack of authentication made the lookup easy to MITM. We considered DNSSEC, but due to limited deployment and difficult setup, we felt that was the wrong solution. We opted for DNS-over-HTTPS instead. How it works. When a Dat URL with a shortname such as dat:// is loaded, Beaker makes a GET request to https:// /.well-known/dat. The response lo...

~?~

~?~

~?~