31–40 of 111 posts
Earlier quoted context omitted.
maybe on a wifi network before authentication when it may allow DNS resolution but not HTTP requests?
Could you shuttle more data through this method to have a browser that works on unauthenticated captive portal wifi networks?
I think it would work to use "time" etc as subdomains instead of TLD to be able to use any DNS server for the query.
> dig pi.neomantra.net +short
3.141.59.26
> dig pi.neomantra.net +short -t AAAA
3141:5926:5358:9793:2384:6264:3383:2795
“Why? For fun.” I love this. It doesn’t need a reason to exist. It’s interesting on its own. That being said, can anyone think of additional interesting reasons for why this would be useful rather than the same toys over HTTP?
Simplicity / latency / efficiency - DNS typically just fires off one UDP packet (generally one IP packet & ethernet frame too) and then gets one back (hopefully) and it's done. HTTP requires the TCP 3-way connection handshake, then the out & back roundtrip for request/response, then the 4-way teardown handshake. If it's HTTPS you also need the 4-way TLS Anyway if you're using a 14.4 modem in a rusty bunker at the bot…
Neat! For unit conversions there is an older tool called 'unit' which can convert nearly anything.
units -t '12 * 45 * 11'
units -t '(8 lbf) / (9.8 m/s^2)' slug
Correct way (absolute temperature):
units -t 'tempF(71)' tempC
units -t '71 degF' degC
# in-terminal calculator: e.g. `calc 60 * 60 * 4`
_calc () {
units -t "$*"
}
alias calc='noglob _calc'
# units convenience, use ( and * without quoting
alias u='noglob units -t'