Live data from Hacker News

HTML over DNS: Serving Blog Content over DNS

jacobkiers.net

31–40 of 77 posts

Re: HTML over DNS: Serving Blog Content over DNS

#31
post #23
post #22

Earlier quoted context omitted.

Been wondering about this, how many people are using old browsers? caniuse.com reports [0] 96% support for ES6 classes. The other 4% is divided between Internet Explorer, Opera Mini and obsolete versions of every other browser. So I'm trying to figure out what kind of people are using such ancient technology and why? What kind of unusual visitors would I be missing out on?

You're missing on visitors with disabled (or whitelisted) javascript. On HackerNews that'll be pretty common.

Does anyone have a recommendation for a JavaScript whitelisting extension or method for macOS Safari?

Re: HTML over DNS: Serving Blog Content over DNS

#32
post #20

Earlier quoted context omitted.

Apparently uses DoH. I don't think dig(1) talks DoH, you'd have to use curl or kdig.

DNS is DNS. You should be able to talk to the NS with DNS over UDP, TCP, or HTTP(s). The protocol used should not matter. The information received should be always the same.

...in an ideal world

Re: HTML over DNS: Serving Blog Content over DNS

#33
post #28

Corollary is, spyware can use DNS to exfiltrate data [0]. Or, send out client-side metrics with cleverly drafted DNS requests [1], or use it as a 3p-cookie replacement [2]. [0] https://unit42.paloaltonetworks.com/dns-tunneling-how-dns-ca... [1] https://github.com/Jigsaw-Code/choir (disclosure: I co-develop hard-forks of two other related Jigsaw-Code projects) [2] http://dnscookie.com/

Packet size is a really good detection for this. DNS packets should only be so big ;)

[deleted]

Re: HTML over DNS: Serving Blog Content over DNS

#34
post #23
post #22

Earlier quoted context omitted.

Been wondering about this, how many people are using old browsers? caniuse.com reports [0] 96% support for ES6 classes. The other 4% is divided between Internet Explorer, Opera Mini and obsolete versions of every other browser. So I'm trying to figure out what kind of people are using such ancient technology and why? What kind of unusual visitors would I be missing out on?

You're missing on visitors with disabled (or whitelisted) javascript. On HackerNews that'll be pretty common.

It's true that people with JavaScript disabled won't be able to run any JavaScript, but once they turn it on it should have relatively good feature support -- I suspect the sort of people who know how to disable JavaScript aren't using software more than 5 years out of date.

Re: HTML over DNS: Serving Blog Content over DNS

#35

> You might not be able to see it immediately Or at all since the content is entirely injected via JS with no fallback (and the JS uses class fields in case you thought an old browser might be able to load it).

I don't know how to do this without JS. Also, since this was mostly a DNS-focused proof of concept, I don't particularly care about that. Not in this case, at least.

You don’t have to “do this without JS” but you could have a fallback to tell JS-less users about it. As is they get a blank page and no idea what’s happening.

Re: HTML over DNS: Serving Blog Content over DNS

#36
post #22

> You might not be able to see it immediately Or at all since the content is entirely injected via JS with no fallback (and the JS uses class fields in case you thought an old browser might be able to load it).

Been wondering about this, how many people are using old browsers? caniuse.com reports [0] 96% support for ES6 classes. The other 4% is divided between Internet Explorer, Opera Mini and obsolete versions of every other browser. So I'm trying to figure out what kind of people are using such ancient technology and why? What kind of unusual visitors would I be missing out on?

> caniuse.com reports [0] 96% support for ES6 classes.

Class fields are later addition to classes. And completely unnecessary here, it looks. The class fields are just duplicates of the instance fields, which are always filled.

> The other 4% is divided between Internet Explorer, Opera Mini and obsolete versions of every other browser. So I'm trying to figure out what kind of people are using such ancient technology and why?

Unsupported device which can not have recent updates for one reason or an other?

Re: HTML over DNS: Serving Blog Content over DNS

#37
post #34
post #23

Earlier quoted context omitted.

You're missing on visitors with disabled (or whitelisted) javascript. On HackerNews that'll be pretty common.

It's true that people with JavaScript disabled won't be able to run any JavaScript, but once they turn it on it should have relatively good feature support -- I suspect the sort of people who know how to disable JavaScript aren't using software more than 5 years out of date.

> but once they turn it on it should have relatively good feature support

How could they even know to tuen it on when all they get is an empty page?

Re: HTML over DNS: Serving Blog Content over DNS

#39

Corollary is, spyware can use DNS to exfiltrate data [0]. Or, send out client-side metrics with cleverly drafted DNS requests [1], or use it as a 3p-cookie replacement [2]. [0] https://unit42.paloaltonetworks.com/dns-tunneling-how-dns-ca... [1] https://github.com/Jigsaw-Code/choir (disclosure: I co-develop hard-forks of two other related Jigsaw-Code projects) [2] http://dnscookie.com/

[deleted]

Re: HTML over DNS: Serving Blog Content over DNS

#40
post #26

Well the content is stored in a DNS Zone file but it is requested using JavaScript to an external HTTP API. I wouldn't really call that HTML over DNS but rather "DNS Zone as blog database". Anyway, this made me think of iodine [1], an IP over DNS solution, which I still run on my main server even though it has a lot less use now than it had until a few years ago when there were a lot of open wifi with captive portals…

the site is down? - https://code.kyro.se/iodine/
Post reply on HN