4 ms·
Hey all. This is the second time I'm submitting Beaker. First time was back in august.[1] Since then, we've done a lot to improve the browser and build on the
by pfraze 10y ago
Hey all. This is the second time I'm submitting Beaker. First time was back in august.[1]
Since then, we've done a lot to improve the browser and build on the ideas. I've written about the P2P Web here[2], and there's a talk at the Web 1.0 conference[3] that goes into more depth if you're still curious.
Happy to answer any questions. Architecture/scaling, privacy, FOSS on the Web, etc.
1 https://news.ycombinator.com/item?id=12270762 https://news.ycombinator.com/item?id=12270762
2 http://pfrazee.github.io/blog/what-is-the-p2p-web http://pfrazee.github.io/blog/what-is-the-p2p-web
3 https://youtu.be/pi-kreA52oI https://youtu.be/pi-kreA52oI
- teaearlgraycold 10y agoWhen you re-host a website, do updates to the original site get pushed to your computer for you to re-host? If not, are you notified?
- pfraze 10y agoEach Dat is controlled by an append-only log. When you swarm a dat, you poll for updates to the log via UDP, which is low cost. (I think Mafintosh may have put in a push mechanism too.) So yes, you are notified. That's why Beaker is able to do live reloading.
- leni536 10y agoWhy don't you use ipfs as the backend? The dat protocol and ipfs seem to share similar goals.
- neilellis 10y agoGreat work, making the web fun and easy to use is a fantastic goal.