I was installing IIS on my Vista box earlier to test out Habari without mod_rewrite and happened to see this as I was finishing up:
Where did you come from? I sure didn’t install you…
AT&T 3G Coverage, iPhone Upgrade here I come!
Several times leading up to the iPhone 3G launch, I checked AT&T’s coverage map to see where they offered 3G coverage. I knew there was no coverage in my immediate area (Greenville, SC), so I was looking forward to finding a job in Charlotte, NC where they had very good 3G coverage.
Low and behold, while looking at a PC World article criticizing the 3G coverage, I load up the coverage map today and find that they have Greenville marked as a 3G area. Kick ass! Time to track down a store with an iPhone in stock so I can upgrade!
Giving Money and Power to Government
Giving money and power to government is like giving whiskey and car keys to teenage boys.
Meta Name = Color?
I was looking at the source code of the Twitter Status blog, mainly out of curiosity to see how Tumblr was put together, and the first thing I noticed was this odd block of meta tags at the very top of the header:
<!-- DEFAULT COLORS -->
<meta name="color:Background" content="#fff"/>
<meta name="color:Title" content="#444"/>
<meta name="color:Description" content="#777"/>
<meta name="color:Post Title" content="#6498cc"/>
<meta name="color:Text" content="#444"/>
<meta name="color:Inline Link" content="#6498cc"/>
<meta name="color:Quote" content="#888"/>
<meta name="color:Quote Border" content="#6498cc"/>
<meta name="color:Quote Source" content="#555"/>
<meta name="color:Link Post" content="#c00"/>
<meta name="color:Conversation Background 1" content="#f4f4f4"/>
<meta name="color:Conversation Background 2" content="#e8e8e8"/>
<meta name="color:Conversation Border" content="#bbb"/>
<meta name="color:Conversation Text" content="#444"/>
<meta name="color:Date" content="#ccc"/>
<meta name="color:Date Block" content="#6498cc"/>
<meta name="color:Date Block Text" content="#bbd5f1"/>
<!-- END DEFAULT COLORS -->Can someone tell me what the hell that accomplishes?
IETester and Javascript Errors
I was playing with IETester, which lets you open Internet Explorer tabs using rendering engines from IE 5.5 up to IE 8 beta 1 for testing compatibility, and noticed for the first time that my blog was throwing a Javascript error only in IE.
Being the pain in the ass IE is, of course the line number it gives isn’t really valid. I looked and looked and couldn’t find the problem. As a last ditch effort, using the IE Developer Toolbar, I hit the menu option to validate the page. Thanks to the W3C Validator, I found that there were some duplicate ID attributes on elements.
After checking out the lines the validator referenced, I found that the Google Analytics plugin for WordPress was improperly tearing apart href attributes for links created by the Footnotes plugin I use, causing it to include long strings of HTML in the onclick attribute for tracking outgoing links1.
Thankfully, the Analytics plugin has an option to turn off outbound link tracking. I’ll miss those stats, but it’s not like I pay all that much attention to them (or care) anyway.
In the end, I don’t really have anything to test with IETester, it was just a fun toy for a few minutes. It also helped me notice a problem I probably wouldn’t have found otherwise, so in the end it was time well spent.
- Rather than just the link the user was headed for, as it should – and does for regular links. [↩]