Is Beaker tied to Chromium? It looks that way from the screenshots, which is disappointing as a Firefox user/contributor.
It's a chromium fork, yeah.
Re:Announcing DatHTTPD
by statictyper on Thursday February 23, 2017 @01:57PM
(#13716640)
Is taking a more secure baseline part of the plan? I'm thinking of https://github.com/Eloston/ungoogled-chromium
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, what's the point?)
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.
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.
That's not far off from what we're thinking.
What about storing the dat link in a TEXT dns record?
We did that originally, but there's no authentication so it would be trivial to MITM
Re:Announcing DatHTTPD
by statictyper on Thursday February 23, 2017 @02:01PM
(#13716670)
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.
Happy to answer questions.
1. https://beakerbrowser.com/
EDIT: direct link to the repo 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.