<?xml version="1.0" encoding="utf-8"?>

			<rss version="2.0" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:cc="http://web.resource.org/cc/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd">

			<channel>
			<title>Ben Forta&apos;s Blog - Stuff</title>
			<link>http://forta.com/blog/index.cfm</link>
			<description>The web, app development, mobile, ColdFusion, gadgets, and whatever else tickles my fancy.</description>
			<language>en-us</language>
			<pubDate>Sun, 26 May 2013 01:10:58 -0400</pubDate>
			<lastBuildDate>Fri, 23 Nov 2012 14:00:00 -0400</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>ben@forta.com</managingEditor>
			<webMaster>ben@forta.com</webMaster>
			<itunes:subtitle></itunes:subtitle>
			<itunes:summary></itunes:summary>
			<itunes:category text="Technology" />
			<itunes:category text="Technology">
				<itunes:category text="Podcasting" />
			</itunes:category>
			<itunes:category text="Technology">
				<itunes:category text="Tech News" />
			</itunes:category>
			<itunes:keywords></itunes:keywords>
			<itunes:author></itunes:author>
			<itunes:owner>
				<itunes:email>ben@forta.com</itunes:email>
				<itunes:name></itunes:name>
			</itunes:owner>
			
			<itunes:explicit>no</itunes:explicit>
			
			<item>
				<title>Welcome To The New forta.com</title>
				<link>http://forta.com/blog/index.cfm/2012/11/23/Welcome-To-The-New-fortacom</link>
				<description>
				
				With any luck (and with the cooperation of the DNS gods) you should be reading this on my new and improved personal web site. This is the first complete redesign of this site in over a decade, and I&apos;m really pleased with how it has turned out.

This site has evolved slowly (OK, it&apos;s worse than that, I know) for more than a decade. It started out as a resource for ColdFusion developers, and then turned into a support site for my &lt;a href=&quot;http://forta.com/books/&quot;&gt;books&lt;/a&gt;. And now it&apos;s both, and more, and perhaps most importantly, it&apos;s a playground for me to keep playing with coding, development ideas, and new technologies. Or at least that&apos;s what I had been trying to convince myself. The reality is that the site was stuck in a time warp, the web circa late &apos;90s or so, complete with nested tables for all layout and alignment, embedded font tags and explicit sizing, images containing formatted text, ugly sprawling JavaScript that I had little control over ... you get the idea. And honestly, I did start work on a revamped site more than once. But between the back-end code, the design, the weight of pages, and more, I never seemed to like where I ended up, and so, well, the old site worked and so it lived on. Until today.For this new site I had a few important goals:

&lt;ul&gt;
&lt;li&gt;A cleaner, more modern look and feel.&lt;/li&gt;
&lt;li&gt;Pure CSS for all layout and design (and not a single HTML table for anything other than tabular data).&lt;/li&gt;
&lt;li&gt;Exceedingly lightweight pages with no extraneous code.&lt;/li&gt;
&lt;li&gt;Highly performant (this one is an outcome of the two prior bullets, but is also thanks to sophisticated caching where appropriate).&lt;/li&gt;
&lt;li&gt;And perhaps most importantly considering the growing percentage of traffic coming from tablets and smartphones, a &lt;a href=&quot;http://en.wikipedia.org/wiki/Responsive_web_design&quot;&gt;responsive design&lt;/a&gt;, one that would adapt to any screen size and look right. (The alternative was a mobile version of the site, a m. site, a practice I am not a fan of). If you are not sure what this means, try looking at this page (or the &lt;a href=&quot;http://forta.com/blog&quot;&gt;blog&lt;/a&gt; or a &lt;a href=&quot;http://forta.com/books/0672336073/&quot;&gt;book&lt;/a&gt; page) on devices with small screens, or just drag your browser to make it narrower, or if you are using an iPad or a Nexus 7 try any of those pages while rotating between portrait and landscape. Pretty slick, huh?&lt;/li&gt;
&lt;/ul&gt;

Obviously, the back end is all &lt;a href=&quot;http://www.adobe.com/go/coldfusion&quot;&gt;ColdFusion&lt;/a&gt;. The underlying databases did not change at all, but the middle tier and presentation layer were rewritten from scratch so as to use ColdFusion for what it does best, and to stop using it where it no longer makes sense to do so. Site structure and URLs were all maintained so as to not break existing links, but where possible I opted to use better and more modern ways of doing things (serving &lt;a href=&quot;http://forta.com/about/ontheroad/&quot;&gt;photo albums&lt;/a&gt; from Flickr instead of managing them myself, as an example). I&apos;ve posted some details on the libraries and services used on the &lt;a href=&quot;http://forta.com/about/&quot;&gt;About&lt;/a&gt; page.

The only section of the site that I did not bring over is the ColdFusion section. That used to host useful links most of which were no longer useful (and some were no longer even links), the user submitted and maintained &amp;quot;Who&apos;s Using ColdFusion?&amp;quot; list that had become so out of date that it had ceased to be of value, and the ColdFusion ISP list which had also gotten out of date and which frankly is just less needed in this Google search era. That aside, everything else is here, and everything seems to be working well.

Of course, it is possible (even likely) that you&apos;ll come across errors or bugs or things that just look odd. And if that were to occur, please let me know via email or in a comment below.

And as usual, your comments and feedback are welcome and appreciated.
				</description>
				
				<category>Stuff</category>
				
				<category>ColdFusion</category>
				
				<category>HTML5</category>
				
				<pubDate>Fri, 23 Nov 2012 14:00:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2012/11/23/Welcome-To-The-New-fortacom</guid>
				
				
			</item>
			
			<item>
				<title>Yes, It Is A Big Deal</title>
				<link>http://forta.com/blog/index.cfm/2012/8/6/Yes-It-Is-A-Big-Deal</link>
				<description>
				
				An acquaintance apparently saw my exuberantly gushing Curiosity posts and tweets, and IMd me with &amp;quot;that big a deal, huh?&amp;quot;.

It took me a few minutes to figure out how to respond, how to capture the pride and emotion and admiration. But, I tried to do just that, and this is what I sent back:At the risk of sounding pompous, in the annals of space exploration, Curiosity&apos;s landing on Mars has to count as one of the most significant milestones. How significant? The Apollo 11 mission in 1969 placed humans on the moon, that was hugely significant, it changed how we thought about science and space travel and human endeavors, and inspired a generation to think big. The Space Shuttle program in the 1980s made space travel almost appear normal and even easy, reusable launch systems and vehicles completed 135 launches the vast majority of which never received any news coverage because going to space had become so routine, that is until Challenger and Columbia reminded us of how dangerous each mission really is. Apollo 11 and the Shuttle program changed our perceptions of what is humanly possible. They moved the bar between the doable and the unfathomable. They rewrote the book on scientific accomplishments and engineering ingenuity, and reminded us that the inconceivable can soon become anything but. They made math and the sciences cool, and made anything seem possible.

And the way I see it, Curiosity is just as significant. Engineers and scientists spent more than a decade conceiving and building a one-ton nuclear powered robot (yes, Curiosity is a robot) the size of a car. Curiosity is now a long way from home, it traveled millions of miles for 36 weeks to reach Mars, and then it had to land itself using maneuvers that would make an Olympic gymnast shrink in fear. And engineers had to plan it all, thinking through every scenario and what-if, speculating about anything that could go wrong, anticipating any contingency, teaching Curiosity everything it needs to know so that it could autonomously execute an utterly audacious landing. Mars is 34,000,000 miles away when it is closest to us, so replacing parts is not an option, nor are manufacturer recalls, or scheduled maintenance - Curiosity has to make do with whatever she left home with back in November 2011. Oh, and there was no real way to test this thoroughly, the trial-run was the actual landing a few hours ago. And it worked, flawlessly!

Curiosity is going to send us incredible pictures and data for a long time to come, at least for a complete Mars year. And if prior rovers are an indicator, Curiosity should be keeping us busy for much longer than that. But even if we were to never hear from Curiosity again, the successful landing is already hugely significant in that it has already moved that bar once again. Forget HAL and R2D2 and Marvin the Paranoid Android, Curiosity is a real robot, an incredibly intelligent and capable machine built by man, a machine that will force us to once again rethink the impossible and the inconceivable.

Years from now you&apos;ll remember where you were when Curiosity proudly announced that it had planted its wheels on Mars, and you&apos;ll never forget the scenes of hugs and tears and jubilant cheers being broadcast from NASA JPL.

So, yeah, this is a big deal, a big fat freaking huge deal!
				</description>
				
				<category>Stuff</category>
				
				<pubDate>Mon, 06 Aug 2012 11:27:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2012/8/6/Yes-It-Is-A-Big-Deal</guid>
				
				
			</item>
			
			<item>
				<title>Tarmac Delay Rule Shocker - NOT!</title>
				<link>http://forta.com/blog/index.cfm/2011/11/14/Tarmac-Delay-Rule-Shocker-NOT</link>
				<description>
				
				Back when the &lt;a href=&quot;http://www.dot.gov/affairs/2009/dot19909.htm&quot;&gt;tarmac delay rule&lt;/a&gt; went into effect I &lt;a href=&quot;http://forta.com/blog/index.cfm/2010/4/27/New-Tarmac-Delay-Rule-Is-NOT-Good-News&quot;&gt;predicted&lt;/a&gt; that this rule would fall victim to the &lt;a href=&quot;http://en.wikipedia.org/wiki/Law_of_Unintended_Consequences&quot;&gt;Law of Unintended Consequences &lt;/a&gt; and that &lt;em&gt;airlines will do the only thing they can do, they&apos;ll cancel flights earlier or more often&lt;/em&gt; (that copied and pasted from an April 2010 &lt;a href=&quot;http://forta.com/blog/index.cfm/2010/4/27/New-Tarmac-Delay-Rule-Is-NOT-Good-News&quot;&gt;blog post&lt;/a&gt;).

And so I was not in the least bit surprised to see the &lt;a href=&quot;http://www.gao.gov/new.items/d11733.pdf&quot;&gt;report from the US Government Accountability Office&lt;/a&gt; proclaim that &lt;em&gt;our analysis has shown that the rule appears to be associated with an increased number of cancellations for thousands of additional passengers - far more than DOT initially predicted - including some who might not have experienced a tarmac delay&lt;/em&gt;.

I know I shouldn&apos;t say &amp;quot;I told you so&amp;quot;, but ...
				</description>
				
				<category>Stuff</category>
				
				<pubDate>Mon, 14 Nov 2011 12:00:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2011/11/14/Tarmac-Delay-Rule-Shocker-NOT</guid>
				
				
			</item>
			
			<item>
				<title>When Lightning Strikes The Network</title>
				<link>http://forta.com/blog/index.cfm/2011/8/4/When-Lightning-Strikes-The-Network</link>
				<description>
				
				My home network had a bad week last week. One of my 24 port hubs is dead (well, it powers up and passes POST, but not a single data LED lights up). The WAN port on my SonicWALL firewall is fried (fortunately I had an unused port and was able to change the configuration to get back online). My Roku box no longer works on wired Ethernet (although it does work on Wi-Fi). I lost one port on my PBX. A VGA over Cat5 extender lost all 4 of its ports. The integrated Ethernet port on one of my computers is dead. It could have been much worse. I have lots of connected equipment and the vast majority of it is fine (the pattern around what was fried and what not is intriguing to say the least). Still, as I said, a bad week.

The culprit? A massive lightning storm in the area. We never lost power, but apparently the lightning must have caused a significant surge and fried lots of equipment connected to the phone lines (several POTS voice lines and a U-verse data line). Interestingly, all of the damaged equipment still works, I just lost lots and lots of ports, almost all on my LAN, and one on a PBX daughterboard.

I have significant power surge protection. But, obviously, none for the phone and data lines that come into my house. And while I know that this was a freak occurrence, it&apos;s still been frustrating and expensive enough that I&apos;ve been looking into the options for protecting phone and data. And the information out there is rather ambiguous, ranging from inline solutions with mixed reviews, to comments about the impact on performance, and more.

So, I&apos;d like your input. If you have any experience with this type of surge protection, please share - the good, the bad, and the ugly is all appreciated. Thanks!
				</description>
				
				<category>Stuff</category>
				
				<pubDate>Thu, 04 Aug 2011 21:11:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2011/8/4/When-Lightning-Strikes-The-Network</guid>
				
				
			</item>
			
			<item>
				<title>Vote For Matt Gifford</title>
				<link>http://forta.com/blog/index.cfm/2011/7/29/Vote-For-Matt-Gifford</link>
				<description>
				
				.net Magazine is running their annual .net Awards, and our own Matt Gifford is the only ColdFusion developer up for a &lt;a href=&quot;http://www.thenetawards.com/&quot;&gt;.net Awards 2011&lt;/a&gt;. Feel free to help him out, go vote (category 16, at the bottom).
				</description>
				
				<category>Stuff</category>
				
				<pubDate>Fri, 29 Jul 2011 00:21:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2011/7/29/Vote-For-Matt-Gifford</guid>
				
				
			</item>
			
			<item>
				<title>BrowserLab Updated</title>
				<link>http://forta.com/blog/index.cfm/2011/6/11/BrowserLab-Updated</link>
				<description>
				
				The &lt;a href=&quot;http://browserlab.adobe.com/&quot;&gt;BrowserLab&lt;/a&gt; team has &lt;a href=&quot;http://blogs.adobe.com/browserlab/2011/06/09/browserlab-1-6-1-is-live-now-with-chrome-11/&quot;&gt;announced&lt;/a&gt; that version 1.6.1 is now live, and includes support for newer versions of Chrome (although not the newest yet).
				</description>
				
				<category>Stuff</category>
				
				<pubDate>Sat, 11 Jun 2011 23:14:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2011/6/11/BrowserLab-Updated</guid>
				
				
			</item>
			
			<item>
				<title>Expanding A Virtual PC Hard Drive</title>
				<link>http://forta.com/blog/index.cfm/2011/5/30/Expanding-A-Virtual-PC-Hard-Drive</link>
				<description>
				
				I use &lt;a href=&quot;http://www.microsoft.com/windows/virtual-pc/default.aspx&quot;&gt;Virtual PC&lt;/a&gt; extensively, and have lots of virtual machines that I fire up as needed to run specific software. (&lt;a href=&quot;http://www.carehart.org/&quot;&gt;Charlie Arehart&lt;/a&gt; gets the credit for getting me hooked on virtual computers many years ago). Virtual computers use virtual hard drives, essentially a complete hard drive in a single file, a .vhd file. When a virtual hard drive is created you specify a maximum size, and the drive can either grow to that size as needed (dynamic drive) or start off as the specified size (fixed drive).

But what if you need to expand a drive beyond that initially designated size? There is a great little free utility named &lt;a href=&quot;http://vmtoolkit.com/default.aspx&quot;&gt;VHD Resizer&lt;/a&gt;, which, as its name suggests, resizes VHD (virtual hard drive) files. It can convert between dynamic and fixed sized virtual drives, and can change the drive size, too. Simple, right? Well, not quite.

Here&apos;s the problem. Expanding the size of virtual drive is simple enough, but expanding the size will not automatically resize partitions on the drive. So, if for example you expanded a 4GB virtual drive to 8GB, your C: drive on the virtual drive will still be 4GB in size, and the extra space will be unassigned waiting for you to create a new drive (perhaps drive D:). Which is great, unless you really do need to expand drive C:, as I just did.

Windows includes a command line utility named &lt;a href=&quot;http://support.microsoft.com/kb/300415&quot;&gt;diskpart&lt;/a&gt; which can extend partitions, but diskpart cannot be used for system or boot volumes, and so if you boot from drive C: (usually the case) you&apos;ll not be able to extend it. There are 3rd party tools which can indeed manipulate partitions, including extending system partitions. But (at 36,000 feet somewhere over CO) I found a workaround.

WARNING: What follows is NOT recommended by Microsoft. It worked for me, but no promises. In other words, if you&apos;re going to attempt this, make sure you&apos;ve backed up your .vhd file. And if it doesn&apos;t work, well, I don&apos;t want to know! ;-)

Ok, so here&apos;s what I did:

&lt;ol&gt;
&lt;li&gt;You&apos;ll need two virtual computers, let&apos;s call the one whose drive you want expanded A, and the second B&lt;/li&gt;
&lt;li&gt;Make sure virtual computers A and B are not running&lt;/li&gt;
&lt;li&gt;Open the settings for virtual computer B, you&apos;ll likely see a virtual hard drive listed as Hard Disk 1, and Hard Disk 2 through 4 will be empty&lt;/li&gt;
&lt;li&gt;Set Hard Disk 2 to point to the .vhd file used by virtual computer A&lt;/li&gt;
&lt;li&gt;Save settings and fire up virtual computer B&lt;/li&gt;
&lt;li&gt;Once virtual computer B is running you&apos;ll see its own virtual hard drive as drive C:, and virtual computer A&apos;s hard drive as another letter (next available letter) &lt;/li&gt;
&lt;li&gt;On virtual computer B, open a command prompt and run diskpart, selecting the volume that is computer A&apos;s virtual hard drive, and extend it (this will be allowed as diskpart won&apos;t recognize it as a system partition as you didn&apos;t actually boot virtual computer B from it)&lt;/li&gt;
&lt;li&gt;Shut down virtual computer B, and remove the added hard drive from its settings&lt;/li&gt;
&lt;li&gt;Now fire up virtual computer A&lt;/li&gt;
&lt;li&gt;With any luck you&apos;ll now have an expanded system volume&lt;/li&gt;
&lt;/ol&gt;

This is NOT supposed to work safely. But, I just did it, and it worked perfectly. Great little workaround, but, caveat emptor.
				</description>
				
				<category>Stuff</category>
				
				<pubDate>Mon, 30 May 2011 17:40:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2011/5/30/Expanding-A-Virtual-PC-Hard-Drive</guid>
				
				
			</item>
			
			<item>
				<title>BrowserLab For Firebug Updated</title>
				<link>http://forta.com/blog/index.cfm/2011/4/4/BrowserLab-For-Firebug-Updated</link>
				<description>
				
				&lt;a href=&quot;http://browserlab.adobe.com/&quot;&gt;BrowserLab&lt;/a&gt; is our online service for performing cross browser testing, and BrowserLab for Firebug is a Firefox add-on that lets you preview temporary changes you&apos;ve made using. Today the BrowserLab team &lt;a href=&quot;http://blogs.adobe.com/browserlab/2011/04/04/browserlab-for-firebug-update/&quot;&gt;announced&lt;/a&gt; that BrowserLab for Firebug has been updated to support Firefox 4 and Firebug 1.7.
				</description>
				
				<category>Stuff</category>
				
				<pubDate>Mon, 04 Apr 2011 23:50:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2011/4/4/BrowserLab-For-Firebug-Updated</guid>
				
				
			</item>
			
			<item>
				<title>Serge Jespers Interviews Paul Gubbay Re HTML5</title>
				<link>http://forta.com/blog/index.cfm/2011/3/28/Serge-Jespers-Interviews-Paul-Gubbay-Re-HTML5</link>
				<description>
				
				Paul Gubbay is Adobe&apos;s VP of Design and Web Engineering. You may recall that I interviewed him (and John Resig) during the &lt;a href=&quot;http://2010.max.adobe.com/&quot;&gt;MAX 2010&lt;/a&gt; Day 2 keynote, and we chatted about HTML5, jQuery, and more. Well, Paul has been &lt;a href=&quot;http://vimeo.com/21296709&quot;&gt;interviewed&lt;/a&gt; again, this time at FITC by fellow Adobe evangelist Serge Jespers:

&lt;iframe src=&quot;http://player.vimeo.com/video/21296709&quot; width=&quot;400&quot; height=&quot;225&quot; frameborder=&quot;0&quot;&gt;&lt;/iframe&gt;
				</description>
				
				<category>MAX</category>
				
				<category>Stuff</category>
				
				<category>AdobeMAX10</category>
				
				<pubDate>Mon, 28 Mar 2011 17:10:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2011/3/28/Serge-Jespers-Interviews-Paul-Gubbay-Re-HTML5</guid>
				
				
			</item>
			
			<item>
				<title>Thank You, Discovery</title>
				<link>http://forta.com/blog/index.cfm/2011/3/9/Thank-You-Discovery</link>
				<description>
				
				&lt;img src=&quot;http://upload.wikimedia.org/wikipedia/commons/thumb/3/36/STS-124_Discovery_Launch1.jpg/200px-STS-124_Discovery_Launch1.jpg&quot; align=&quot;left&quot; height=&quot;305&quot; width=&quot;200&quot;&gt;I am on a Delta flight from SFO to DTW. Fortunately, the plane is equipped with Wi-Fi, so I was able to watch &lt;a href=&quot; http://en.wikipedia.org/wiki/Space_Shuttle_Discovery&quot;&gt;Space Shuttle Discovery&lt;/a&gt;&apos;s final landing on NASA TV. And honestly, this picture perfect farewell is stirring up a mix of emotions and reactions.

I remember as a teen back in the 80&apos;s reading up on everything I could find about the Shuttle fleet as they were being built. I still remember the reaction at seeing a picture of a Shuttle piggy-backed on a Boeing 747 for the first time. I remember exactly where I was (in a taxi in Manchester, England) back in 1986 when we heard about the Space Shuttle Challenger disaster, and the exhilaration listening live to Discovery triumphantly reinvigorate the program two years later with mission STS-26. And I recall the horrible sense of d&#xe9;j&#xe0; vu when Columbia disintegrated upon reentry in 2003, and the similar nervous tension three years later when again Discovery led the way back to space with mission STS-116. And I know I am not alone, millions have the same emotional attachment to an amazing and awe-inspiring machine.

And the emotions? Pride, exhilaration, awe ... and at the same time some real anger and disappointment. Honestly, it feels like we&apos;ve lost the desire to do big bold things, we take Shuttle missions and Space Stations and frequent satellite launches for granted, we&apos;ve grown jaded and uninspired. And worst of all, we&apos;ve lost the healthy curiosity needed to be able to literally aim for the stars. How many kids nowadays want to grow up to be an astronaut?

Realistically, these days we&apos;d never be able to pull off anything as grand and as ambitious as the Space Shuttle program. The public has lost interest and so there is no political will to think big. Considering the huge advances in technology since the Shuttles were conceived and built, we should be planning huge leaps forward in space exploration and associated sciences. But, no, instead we&apos;re having to fight for attention and relevance. I&apos;m sad, disappointed, and yes, angry.

So, welcome home Discovery, farewell, and thank you for 27 inspiring years. And here&apos;s hoping that at some point in the future we&apos;ll once again find the passion, the curiosity, and the willpower to do the impossible and inspire a generation.
				</description>
				
				<category>Stuff</category>
				
				<pubDate>Wed, 09 Mar 2011 12:47:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2011/3/9/Thank-You-Discovery</guid>
				
				
			</item>
			
			<item>
				<title>Trying To Get To Flash Israel, And Thanks For Nothing DOT</title>
				<link>http://forta.com/blog/index.cfm/2011/2/21/Trying-To-Get-To-Flash-Israel-And-Thanks-For-Nothing-DOT</link>
				<description>
				
				I&apos;m go-presenting the &lt;a href=&quot;http://flashisrael.com/&quot;&gt;Flash Israel 2011&lt;/a&gt; opening keynote with Lee Brimelow tomorrow. Or rather, I&apos;m trying to. Weather last night close to shut down DTW, so I never made my connection in JFK. I am now in Amsterdam, and have an 8 hour wait until the flight to TLV. I&apos;ll arrive in the wee hours Tuesday morning, not long before we have to present. Still, I&apos;m really glad to be visiting Israel again, even briefly.

Somewhat related, back in April 2010 I stated that the new DOT 3 Hour Tarmac Delay Rule was a &lt;a href=&quot;http://forta.com/blog/index.cfm/2010/4/27/New-Tarmac-Delay-Rule-Is-NOT-Good-News&quot;&gt;bad idea&lt;/a&gt;. I predicted that it would make airlines overly risk averse, pushing them to return to the gate too early, because canceling flights would be cheaper than risking huge fines. And the pilot on my DTW to JFK flight last night confirmed my fears when he announced that he&apos;d like to wait in the queue longer, that he thought we probably could get out, but that the airline is insisting we deplane because we had just broken the 2 hour mark. Nice, thank you government, you have once again proven how utterly useless you are, and how the &lt;a href=&quot;http://en.wikipedia.org/wiki/Law_of_Unintended_Consequences&quot;&gt;Law of Unintended Consequences&lt;/a&gt; is alive and well.

Ok, now what to do for 8 hours in Amsterdam?
				</description>
				
				<category>Stuff</category>
				
				<category>Appearances</category>
				
				<pubDate>Mon, 21 Feb 2011 07:23:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2011/2/21/Trying-To-Get-To-Flash-Israel-And-Thanks-For-Nothing-DOT</guid>
				
				
			</item>
			
			<item>
				<title>TSA = Tactics Simply Asinine</title>
				<link>http://forta.com/blog/index.cfm/2010/10/24/TSA-Tactics-Simply-Asinine</link>
				<description>
				
				It&apos;s been a while since I posted examples of TSA rules, policies, and behaviors. But, I just have to share this one:

The primary security entrance at &lt;a href=&quot;http://en.wikipedia.org/wiki/Dtw&quot;&gt;DTW&lt;/a&gt; McNamara Terminal was closed the past couple of weeks while they installed a new &lt;a href=&quot;http://en.wikipedia.org/wiki/Millimeter_wave_scanner&quot;&gt;millimeter wave scanner&lt;/a&gt; (whole body imaging device). Better security, yeah! Or not!

I went through the newly opened security lanes this morning. There is a single millimeter wave scanner sitting to the right of two typical metal detectors. And some passengers are being routed to the new scanner while others are being routed to the metal detectors. Random, right? Well ...

The thing is that there are two entrances to the security area, the left for most of the flying public, and the right for frequent flyers and elite members. In other words, the new scanner is in front of the frequent flyer line.

I stood and watched for a little while, just to see who was getting routed where and how random the routing really is. And sure enough, the majority of passengers directed to the new improved scanning are the ones entering security right in front of the machine. Which passengers? Elite members and frequent flyers, the passengers that the airlines and TSA know best (many of whom have been pre-screened, too)!

Wow, I feel so much safer!
				</description>
				
				<category>Stuff</category>
				
				<pubDate>Sun, 24 Oct 2010 09:44:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2010/10/24/TSA-Tactics-Simply-Asinine</guid>
				
				
			</item>
			
			<item>
				<title>Microsoft By The Numbers</title>
				<link>http://forta.com/blog/index.cfm/2010/8/13/Microsoft-By-The-Numbers</link>
				<description>
				
				Frank X. Shaw, Vice President of Corporate Communications at Microsoft, recently posted an entry entitled &lt;a href=&quot;http://blogs.technet.com/b/microsoft_blog/archive/2010/06/25/microsoft-by-the-numbers.aspx&quot;&gt;Microsoft by the numbers&lt;/a&gt;. Regardless of how you feel about Microsoft or their products, this one provides some very interesting perspective on desktops versus netbooks and tables, smartphone market share, as well as industry income.
				</description>
				
				<category>Stuff</category>
				
				<pubDate>Fri, 13 Aug 2010 17:42:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2010/8/13/Microsoft-By-The-Numbers</guid>
				
				
			</item>
			
			<item>
				<title>InfoWorld: Apple Safari HTML5 Vs. HTML5</title>
				<link>http://forta.com/blog/index.cfm/2010/6/10/InfoWorld-Apple-Safari-HTML5-Vs-HTML5</link>
				<description>
				
				InfoWorld&apos;s Neil McAllister &lt;a href=&quot;http://www.infoworld.com/d/developer-world/apples-html5-promotion-may-backfire-737&quot;&gt;comments&lt;/a&gt; on Apple&apos;s HTML5 drive, and the Web standards community&apos;s displeasure with the effort blasted as being &quot;not intellectually honest&quot;.
				</description>
				
				<category>Stuff</category>
				
				<pubDate>Thu, 10 Jun 2010 14:37:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2010/6/10/InfoWorld-Apple-Safari-HTML5-Vs-HTML5</guid>
				
				
			</item>
			
			<item>
				<title>Google Wi-Fi Sniffing Analogy Is Wrong</title>
				<link>http://forta.com/blog/index.cfm/2010/6/4/Google-WiFi-Sniffing-Analogy-Is-Wrong</link>
				<description>
				
				If I were to leave my house unlocked, I&apos;d not expect people to enter without permission, even though they probably could do so. But if I were having a conversation, perhaps a meeting using a microphone so that everyone could hear, and I left my windows open so that passersby could hear every word, well, I&apos;d have to expect that and be OK with it. No?

Google is in all sorts of trouble over Wi-Fi sniffing by its Street View cars. And &lt;a href=&quot;http://www.wired.com/threatlevel/2010/06/google-wifi-sniffing/&quot;&gt;lawyers now argue&lt;/a&gt; that the data was not collected accidentally as previously claimed, but that the cars were deliberately programmed to collect the data.

And many are comparing this to the unlocked house example, so evil and sinister, big bad Google silently creeping into your private property to steal from you. The thing is, that analogy is flat out inaccurate. My microphone broadcasting info up and down the street is a far more technically accurate analogy. And yes, if you yell outdoors, clearly and free for all to hear, well, then you can&apos;t complain if sometime writes it all down.

Duh!
				</description>
				
				<category>Stuff</category>
				
				<pubDate>Fri, 04 Jun 2010 14:57:00 -0400</pubDate>
				<guid>http://forta.com/blog/index.cfm/2010/6/4/Google-WiFi-Sniffing-Analogy-Is-Wrong</guid>
				
				
			</item>
			</channel></rss>