If you haven't yet tried Sway, the game from Illusion Labs and ReadyFireAim, now's the perfect time to do so. They've released a free version of the game that limits you to three levels and just two characters, but it's enough to try out the really unique control scheme. Back when I first posted about the game, I hadn't tried it yet, but it's now been on my iPhone for about a month, and it's excellent. Each of your thumbs is a "hand" on your characters (i.e., to grab something with your left hand, in game, you just touch your thumb to the left side of the screen), and then once you've grabbed something, you can swipe that thumb back and forth to sway the character around. It gets pretty complex, but practice makes perfect, and a few stages in, you'll be swinging from grip to grip with the greatest of ease.

The full version still costs $4.99, and if you enjoy the free version, I highly recommend it: there are many more characters that you can pick up and choose from, and the stages actually get really tough, as there's a lot of precise swinging that you'll have to do to explore the whole area and find everything there is to find. Sway might be a sleeper hit for the iPhone -- it took me a little while to figure it all out, but once I did, I found a control scheme that's delightfully original. If you haven't tried it out yet, definitely take advantage of the free version.

The iLife Updates Apple released yesterday fixed a gripe some users (including myself) had with the new URL scheme that iWeb employed. With its original release, an iWeb site's URL was http://web.mac.com/username/iWeb/. Leaving that last /iWeb/ off the URL would result in a 404 error. While this isn't a big deal to some, it's just one extra quirky name to add to a URL. To those unfamiliar with the internets however, .Mac and iWeb could mess up, resulting in that exponentially increasing frustration that usually leads to users simply giving up on the endeavor.

After installing the 1.0.1 update last night and making changes to some of my iWeb pages, I was pleased to see the URL in the "announce your site" confirmation window chopped down to simply http://web.mac.com/username. This not only makes the URL a little easier to remember and pass around, it also adds a bit more credibility to the URL, especially over the previous http://homepage.mac.com/username scheme.

Adding to the small pile of gripes with the new technology Apple is using with iLife 06, such as complaints about iWeb's bloated CSS or RSS standards and photocasting, I just developed a beef that I haven't really seen mentioned yet: the crummy new URL scheme for iWeb sites, both on and offline.

First of all, in the olden day the .Mac "homepage" did't seem to be case sensitive, as in: homepage.mac.com/user will get you to the same place as /User. iWeb is a bit pickier, as a wedding site I'm working on lives at web.mac.com/myuser/iWeb/Wedding/, but /wedding/ will result in a 404 error. Yes, a friend already reminded me that "Unix = case sensitive," but I don't care. While this could be labeled a minor complaint, my fiance and I have plenty of family members who aren't too hip on these computer thingies. They're going to get confused by something silly and minor like this, and I'm sure our relatives aren't the only ones.

Next on my list is the URL scheme itself. web.mac.com/user/iWeb/sitename? Could that get any less friendly? Granted "homepage.mac.com" might seems a little unprofessional to some, but this new scheme feels pretty cumbersome and just plain ugly. Why couldn't we simply have web.mac.com/user and web.mac.com/user/othersites, Apple?

Last but not least is how the new sites are organized in a user's iDisk. Old homepage sites still live in iDisk/Sites/, while shiny new iWeb sites live in iDisk/Web/Sites/iWeb/sitename. Nevermind a discussion about how needlessly buried that file structure is - I'm sure this dichotomy of old/new sites and content is going to confuse plenty of .Mac customers if they ever want to get at any of those files, or make a backup of their sites or entire iDisk.

But enough about my gripes, what do you guys think: do iWeb and its underpinning .Mac support have more issues besides CSS and standards? Let's hear your thoughts.