On: Why does pinging 192.168.072 return a response fro...

[aw3c2]

That makes me want to own 222.173.190.239 or 177.107.0.181, just to link to them in hex. If only browsers would keep that in the address bar.

[tspike → aw3c2]

For those too lazy to convert, that's 0xDEADBEEF and 0xB16B00B5, respectively.

EDIT: Fun fact: Chrome's address bar will convert hex IPs for you on the fly. Try typing in http://0xDEADBEEF and look in the suggest box.

[scoot → tspike]

Apparently 0xB16B00B5 made into some Microsoft HyperV code: http://www.bbc.co.uk/news/technology-18922629

Blame? http://www.spinics.net/lists/linux-driver-devel/msg15311.htm...

[rplnt → tspike]

I tried the first one and since I have Google's Feeling Lucky as the default search engine I ended up here http://en.wikipedia.org/wiki/Hexspeak :)

[jevinskie → aw3c2]

Just think of the fun you can have with the bottom 64 bits of an IPv6 address!

[jrockway → jevinskie]

I prefer zeros so I can :: them away.

[guylhem → jevinskie]

Indeed I had lots of fun on my zone - and many big website do this too :-)

Try for ex dig -t aaaa facebook.com

[simcop2387 → aw3c2]

Personally I'd love to get a hold of http://202.254.186.190/ for linking.

[veidelis → simcop2387]

0xCAFEBABE