I’m live blogging the Public Stack Summit.
New web:
dat://live.ar.al/2018/06/19/public-stack-summit/
Old web:
https://
http://live.ar.al/2018/06/19/public-s …
tack-summit/
#publicstacksummit
-
-
Replying to @aral
Is it mandatory to use Google’s DNS to be able to browse Dat? I cannot see your site as I denied access to Google in Little Snitch… :(pic.twitter.com/ZIjUrQBz8I
3 replies 0 retweets 0 likes -
Replying to @skynebula @aral
Validated and trace back to https://github.com/datprotocol/dat-dns/blob/master/index.js … :-( const DEFAULT_DNS_HOST = 'http://dns.google.com '
2 replies 0 retweets 1 like -
Could be overrided there : https://github.com/beakerbrowser/beaker/blob/54ee1f19d8b988ffceab6481f9feaf91f6e46418/app/background-process/networks/dat/dns.js … no PR / issue listed yet on the topic on both projects.
1 reply 0 retweets 0 likes -
Replying to @gillesdemarty @skynebula
Sounds like that could use a PR. Any reason it can’t use an OpenDNS server (or two?)
@pfrazee1 reply 0 retweets 0 likes -
Yeah we use DNS-over-HTTPS right now, to protect MITM attacks on lookups, because Dat has no equivalent to an SSL certificate. (See https://www.datprotocol.com/deps/0005-dns/ ) We can use any DNS-over-HTTPS provider (and also rotate through a whitelist) which I'd be +1 to prioritize
1 reply 0 retweets 2 likes -
So, to summarize, how can we simply use Dat/Beaker without using Google's DNS? (and without doing any PR or compiling anything?) #
1 reply 0 retweets 0 likes -
Nope you got it! We'll need a PR to update this.
1 reply 0 retweets 0 likes
Paul, would you be open to an amendment to the DEP that reverses the order of the lookups so that .well-known (the decentralised option that uses the first-party domain itself) is preferred over the TXT lookup (the centralised option that uses a trusted third party?)
-
-
We're definitely open to those kinds of amendments. Open an issue or a PR herehttps://github.com/datprotocol/deps …
1 reply 0 retweets 0 likes -
Will do, thanks, Paul :)
0 replies 0 retweets 1 like
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.