4 ms·

This is a part of the Beaker p2p browser project [1]. This server lets you host websites over the Dat protocol with DNS shortnames, as well as HTTPS as a fallba

by pfraze 10y ago

This is a part of the Beaker p2p browser project [1]. This server lets you host websites over the Dat protocol with DNS shortnames, as well as HTTPS as a fallback for (let's say) "legacy" browsers. Happy to answer questions. 1. https://beakerbrowser.com/ https://beakerbrowser.com/ EDIT: direct link to the repo https://github.com/beakerbrowser/dathttpd https://github.com/beakerbrowser/dathttpd. We also have Prometheus/Grafana integration which is pretty handy; it's currently the easiest way to watch the health of a swarm.

ploxiln 10y ago
Is there any other way to convert from short-ish names to dat addresses, currently or planned? (If short names always depend on some content hosted at https://same-domain.tld https://same-domain.tld, what's the point?)
- pfraze 10y ago
  Yes - In Beaker we have plans for a userland namespace, which will be under the "app://" scheme. And we may someday move from DNS-over-HTTPS to something like DNSSEC, but that's not planned yet.
  - jvz 10y ago
    I'd love to see a kind of reverse-DNS-style tagging system, so that when my browser comes across a dat:// link it can automatically show me that this content is commonly tagged as "book, Fahrenheit 451" or such.
    - pfraze 10y ago
      That's not far off from what we're thinking.
- gfosco 10y ago
  What about storing the dat link in a TEXT dns record?
  - pfraze 10y ago
    We did that originally, but there's no authentication so it would be trivial to MITM
mintplant 10y ago
Is Beaker tied to Chromium? It looks that way from the screenshots, which is disappointing as a Firefox user/contributor.
- pfraze 10y ago
  It's a chromium fork, yeah.
  - statictyper 10y ago
    Is taking a more secure baseline part of the plan? I'm thinking of https://github.com/Eloston/ungoogled-chromium https://github.com/Eloston/ungoogled-chromium
statictyper 10y ago
Beaker browser is amazing. You seem put most of your efforts on DAT support, do you plan an IPFS support? The historical IPFS implementation is Go but it seems that the JavaScript implementation is gaining traction and, IMO, will become the main reference implementation.

by pfraze 10y ago

ploxiln 10y ago

Is there any other way to convert from short-ish names to dat addresses, currently or planned? (If short names always depend on some content hosted at https://same-domain.tld https://same-domain.tld, what's the point?)

pfraze 10y ago
Yes - In Beaker we have plans for a userland namespace, which will be under the "app://" scheme. And we may someday move from DNS-over-HTTPS to something like DNSSEC, but that's not planned yet.
- jvz 10y ago
  I'd love to see a kind of reverse-DNS-style tagging system, so that when my browser comes across a dat:// link it can automatically show me that this content is commonly tagged as "book, Fahrenheit 451" or such.
  - pfraze 10y ago
    That's not far off from what we're thinking.
gfosco 10y ago
What about storing the dat link in a TEXT dns record?
- pfraze 10y ago
  We did that originally, but there's no authentication so it would be trivial to MITM

mintplant 10y ago

Is Beaker tied to Chromium? It looks that way from the screenshots, which is disappointing as a Firefox user/contributor.

pfraze 10y ago
It's a chromium fork, yeah.
- statictyper 10y ago
  Is taking a more secure baseline part of the plan? I'm thinking of https://github.com/Eloston/ungoogled-chromium https://github.com/Eloston/ungoogled-chromium

statictyper 10y ago

Beaker browser is amazing. You seem put most of your efforts on DAT support, do you plan an IPFS support? The historical IPFS implementation is Go but it seems that the JavaScript implementation is gaining traction and, IMO, will become the main reference implementation.