parkan · October 6, 2019 21:23
diff --git a/Markdium-Shell.bash b/Markdium-Shell.bash

 MOAR
 Of course, this use case is only one stepping stone in the transition to first class decentralized web content everywhere.  The good news is that the design of EthDNS already supports a few more hops into the future:

 on local networks, CoreDNS is a fully featured DNS server, so your conference, meetup, or office can transparently gift ENS+IPNS dweb powers to all visitors by specifying a local EthDNS server in DHCP (we’re going to try setting this up at DevCon 😈)
 because EthDNS returns EIP-1577 IPFS CIDs as TXT records in the widely supported DNSLink format, it’s transparently compatible with all existing IPFS tooling, so you can e.g. use it alongside go-ipfs to supplement decentralized naming in IPNS
 even if the user isn’t configured for DoH, Dapps can still make requests to the resolution endpoint (we’ve enabled CORS allow), so any app that doesn’t want to rely on MetaMask or need full Ethereum API can use a simple XHR call for ENS resolution
 any scenario where running an ethereum client is undesirable can take advantage of ENS name resolution over either classic DNS or DoH

 And likely many more! We want you to grab the plugin, use the DoH in your browser, poke at it with DApps, set it as the DNS in your IoT toaster. Come find us at DevCon and tell us what you’ve resolved!

 PLEASE NOTE: even though we worked very hard on this release and are very proud of it, DNS-over-HTTPS in general, and EthDNS in particular is still a relatively new technology, and should be used with some caution. eth.link is operated by ENS with support from Protocol Labs as an educational and experimental public service with no guarantees, and should not be used for mission-critical applications. Neither ENS or Protocol Labs reviews or retains query logs from this service. We recommend you set up your own EthDNS instance for use with production DApps.

	MOAR
	Of course, this use case is only one stepping stone in the transition to first class decentralized web content everywhere. The good news is that the design of EthDNS already supports a few more hops into the future:

	on local networks, CoreDNS is a fully featured DNS server, so your conference, meetup, or office can transparently gift ENS+IPNS dweb powers to all visitors by specifying a local EthDNS server in DHCP (we’re going to try setting this up at DevCon 😈)
	because EthDNS returns EIP-1577 IPFS CIDs as TXT records in the widely supported DNSLink format, it’s transparently compatible with all existing IPFS tooling, so you can e.g. use it alongside go-ipfs to supplement decentralized naming in IPNS
	even if the user isn’t configured for DoH, Dapps can still make requests to the resolution endpoint (we’ve enabled CORS allow), so any app that doesn’t want to rely on MetaMask or need full Ethereum API can use a simple XHR call for ENS resolution
	any scenario where running an ethereum client is undesirable can take advantage of ENS name resolution over either classic DNS or DoH

	And likely many more! We want you to grab the plugin, use the DoH in your browser, poke at it with DApps, set it as the DNS in your IoT toaster. Come find us at DevCon and tell us what you’ve resolved!

	PLEASE NOTE: even though we worked very hard on this release and are very proud of it, DNS-over-HTTPS in general, and EthDNS in particular is still a relatively new technology, and should be used with some caution. eth.link is operated by ENS with support from Protocol Labs as an educational and experimental public service with no guarantees, and should not be used for mission-critical applications. Neither ENS or Protocol Labs reviews or retains query logs from this service. We recommend you set up your own EthDNS instance for use with production DApps.