2009 Jun 1, 11:07
When I heard that Live Search is now Bing
one of my initial thoughts was how'd they get that domain
name given the unavailability of pronouncable four letter .COM domain names
. Well, the names been used in the past.
Here now, via the Wayback Machine
is a brief, somewhat speculative, and ultimately anticlimactic history
2003 July: The first archived version of bing.com features "bing! is a small device (e.g., possibly even a small
Band-Aid(R)-like sticker!) that vibrates when a person's cell phone rings." I can't recall 2003 cell phones, were they big enough to require this device?
2004 August: Site for the same device is rewritten and looks much better, IMHO.
2006 June: The domain is now parked by easyDNS. I guess the "bing!" device didn't work out?
2006 November: Its now "BING*" and they won't say what they're working on ("we're still in stealth mode") but they are
hiring C#/.NET developers.
2007 January: And they're gone. Without even exiting stealth mode. Too bad, I liked their logo. Their domain is now for
2007 February: Looks like EasyMail buys the domain and offers a physical mailing service in Australia: "By simply clicking
a button on your computer, mail is beamed electronically to a bing post office. Your mail is automatically printed, folded, enveloped and dispatched into the Australia Post network the very same
Present: Now its the new home for Live Search of course.
The new name reminds me of the show Friends. Also, I hope they get a new favicon - I don't enjoy the stretched 'b' nor its color scheme.
2009 May 1, 12:09
"If I'm reading the pop-up window correctly, domain registrar Godaddy recommends against purchasing .tv domain names because the island of Tuvalu, which the domain represents, is sinking."
2009 Feb 5, 8:39
The long expired draft of the Web Proxy Autodiscovery Protocol (WPAD). To summarize, use DHCP and failing that DNS to find the name of a web server and on that web server find a Proxy Auto-Config
file at a well known localtion.
2009 Feb 3, 11:15
"r2719 specifies that browsers should not allow scripts to set document.domain to anything on the Public Suffix List, such as "com" or "co.jp". Essential background reading on why this is dangerous:
Untraceable XSS Attacks. Most browsers already block this attack, e.g. Firefox since 3.0. [Background: Re: Setting document.domain]"
2008 Nov 6, 6:27
Examination of the who and why behind those 'Single?' lawn signs: 'At this point, I came to the realization that every question I answered seemed to introduce two more. In this case, they were "did
someone hire these firms or are they acting on their own?" and, more confusingly, "how did a web design firm in Panama or India get a lawn sign physically planted in the front lawn of my high school
in South Jersey?"'
2008 Nov 5, 9:43
Proposed new arbitrary TLDs are super expensive. As it turns out large companies have to buy their name on every new TLD to avoid potential fraud.
2008 Sep 10, 1:32
Discussion on IETF DNS mailing list about Mozilla's Public Suffix list and what they should do ultimately. "I'm inclined to suggest: Gather and hard-code your list into Firefox, and also provide a
mechanism by which domain authorities can publish information which overrides your list for their domain."
2008 Jul 22, 10:58
"ICANN Generic Names Supporting Organisation - Final Report: Introduction of New Generic Top-Level Domains"
2008 Jul 14, 10:32
Dan Kaminsky's blog.
2008 Jul 14, 10:27
"I'm Dan Kaminsky, and this is my niece Sarah. Sarah has an important message for everybody regarding the Domain Name System."
2008 Jun 30, 3:55
FCC wants nationwide free wifi that's free of porn. They should read this. "Periodically there are proposals to mandate the use of a special top level name or an IP address bit to flag "adult"
"unsafe" material or the like. This document explains why thi
2008 Jun 30, 3:49
Yngve Nysaeter Pettersen briefly talks about his Opera minimal security domain RFCs: "I've just refreshed my HTTP Cookie and Cache related Internet Drafts."
2008 Jun 30, 3:46
Opera's solution to minimal security domain determination: "The drafts describe 1) Opera's current "rule of thumb" implementation that uses DNS in an attempt to confirm the validity of a domain, and
2) a proposed new HTTP based lookup service that retur
2008 Jan 28, 10:39
Name your computer an HTML string to inject that HTML into the target wireless router's HTML configuration page.
2008 Jan 9, 11:34
IPv6 address syntax consists of 8 groupings of colon delimited 16-bit hex values making up the 128-bit address. An optional double colon
can replace any consecutive sequence of 0 valued hex values. For example the following is a valid IPv6 address:
Some IPv6 addresses aren't global and in those cases need a scope ID to describe their context. These get a '%' followed by the scope ID.
For example the previous example with a scope ID of '8' would be:
IPv6 addresses in URIs may appear in the host section of a URI as long as they're enclosed by square brackets. For example:
http://[fe80::2c02:db79]/. The RFC explicitly notes that there isn't a way to add a scope ID to the IPv6 address in a URI. However a draft document describes adding
scope IDs to IPv6 addresses in URIs. The draft document uses the IPvFuture production from the URI RFC with a 'v1' to add a new
hostname syntax and a '+' instead of a '%' for delimiting the scope id. For example:
http://[v1.fe80::2c02:db79+8]/. However, this is still a draft document, not a final
standard, and I don't know of any system that works this way.
In Windows XPSP2 the IPv6 stack is available but disabled by default. To enable the IPv6 stack, at a command prompt run
'netsh interface ipv6 install'. In Vista IPv6 is the on by default and cannot be turned off, while the IPv4 stack is optional and may be turned off by a command similar to the previous.
Once you have IPv6 on in your OS you can turn on IPv6 for
IIS6 or just use IIS7. The address ::1 refers to the local machine.
In some places in Windows like UNC paths, IPv6 addresses aren't allowed. In those cases you can use a Vista DNS IPv6 hack that lives in the OS
name resolution stack that transforms particularly crafted names into IPv6 addresses. Take your IPv6 address, replace the ':'s with '-'s and the '%' with an 's' and then append '.ipv6-literal.net'
to the end. For example:
fe80--2c02-db79s8.ipv6-literal.net. That name will resolve to the same example I've been using in Vista. This transformation occurs inside the system's local
name resolution stack so no DNS servers are involved, although Microsoft does own the ipv6-literal.net domain name.
MSDN describes IPv6 addresses in URIs in Windows and I've described IPv6 addresses in URIs in IE7. File URIs in
IE7 don't support IPv6 addresses. If you want to put a scope ID in a URI in IE7 you use a '%25' to delimit the scope ID and due to a bug you must have at least two digits in your scope ID. So,
to take the previous example:
http://[fe80::2c02:db79%2508]/. Note that its 08 rather than just 8.
2007 Oct 17, 4:48
ICANN's wiki on their new IDN TLDs.
2007 Oct 11, 12:11
ICANN plans to support non-US-ASCII top level domain names. I wonder how broken web browser's security measures are about to become.
2007 Sep 20, 12:20
Article on the fall, division, and name changes of countries affecting top level domain names and vice versa.
2007 Aug 15, 3:20
Listened to RSnake talk about this in person at one point. Pretty interesting without his scenario video with niave female Internet user narration.
2007 May 22, 7:53
Thoughts on determining the effective TLD of a hostname from Mozillaland.