This tutorial documents it, but to get a ad-hoc network the steps look like this:

1. Click ‘create new wireless network
2. Type in some info, click ok
3. Click ‘edit connections’
4. Edit the connection you setup before and change ipv4 settings to use ‘dhcp (automatically)
5. Select your ad-hoc network that is now in the list along with your existing wireless network.

This is super awesome. (This was posted from my iPhone’s 3G Connection, using my laptop)

Bill is a bad ass. He’s a developer and co-founder of squareFACTOR (local super-really-great design and development firm, and I do mean firm). He uses Python and Django to make it happen on the internet, hates php, runs Ubuntu, teaches his children to love Flight of the Conchords, and documents hilarious conversations on THIRTEENPIXELS.

I met Bill when I was looking for work, and although we didn’t end up working together, I was glad to have met him because he’s a good guy. He’s offered his office to me on two occasions (once for OPUG, once for a development sprint with my team from Canonical) and he’s put up with my love for the movie The Happening since we first met.

There you go folks, shows over here. Bill needs to write about some other ‘creative’ in the local area, he has 36 hours to do it.

Of course if he doesn’t he’d still be a pretty great guy, here are the links to the posts so far:

• Joshua Blount
• Bill Evans

1. Thankfully, Canonical is still relatively happy to have me employed. How I got to work with the brilliant people I do is beyond me, but I’m quite excited about it.
2. I find it very difficult to call myself a christian, although I’m making an attempt at living in a similar way to Jesus.
3. I don’t ever want to think about how much money my wife and I are losing on our house at the moment.
4. I simultaneously hate and love our dog, “Baxter Go Blount“
5. I have a mole on the bottom of my right foot. Good to identify me in case of some head injury.
6. Since starting to work from home this past year, I’ve learned that using emoticons keep turf wars and hurt feelings to a minimum.
7. I sometimes wonder if I’m the only one that loves sappy folk music and T-Pain equally. Not that it’s a problem, I’m just curious.

As a side note, sorry about the theme, I felt like it was about time to start writing again, and I simply have no time to go about fixing up this blog at the moment.

Edit:One of the things that I didn’t expect would happen is that this has fixed the long standing issue of Hulu not working (for me).

So, as is my typical modus operandi, I’ve started running again on a whim very late at night. I had a few problems, and I’d love some feedback from the folks I know that are much better at this sort of thing than I am. Please, if you have a moment, fill out this form on WuFoo so that I can gather some of the response and sort out some solutions.

Hooray sweat! Hooray health!

1. Right click on the bluetooth icon in the notification area of the default Hardy desktop and select preferences
2. In the prefenes window select “Visable and connectable for other devices” from the list
3. Click the discoverable button on your keyboard, when it shows up in the prefernces window you have open, click on it and click the trust button. You can now close the preferences window.
4. Right click on the bluetooth icon a second time, this time selecting browse device.
5. Select your keyboard from the list, and click connect.
6. When the error pops up about not being able to connect, notice the mac address (perhaps something like 00:1e:52:fc:87:ea) and leave the error message open so you can type it into the terminal.
7. From the terminal run the following command without the quotes: sudo hidd --connect "the mac address from the error message"
8. Be really happy that you found these instructions instead of pouring through dozens of forum posts with people complaining about their keyboard not working

Awesomeness: 

• I will go into detail later, but the “blank state” for new tabs is beautiful and functional.
• The standard “status bar” at the bottom of most browsers is now a there-when-you-need it popup on the bottom of the screen that disappears when unused. Very thoughtful in regard to screen real-estate. 
• Speaking of screen size, Google has seeming take Safari’s minimalist approach to the next level by removing even the standard File / Edit / etc fields from the Windows version of Chrome. This probably will not work the same way in OS X considering the constantly available menu bar, but it certainly saves some space in Vista / XP.
• The first thing I noticed when testing the browser from within Windows Vista was that Google, by default respects the users preset preference of search engine. Vista comes set (inside of IE7) to default to Live Search and when I launched Chrome for the first time, I a messaging confirming that similar to what you would see in IE7 when first launching. I would have thought Google would just default to it’s own search engine and allow the user to change, so this was a welcome indication of how Google (might) treat their users. 
• Chrome is smoking fast in javascript performance and feels pretty zippy just about everywhere else (launching, opening tabs, etc)
• Chrome uses Webkit, the rendering engine formerly that Apple extracted (and kept open) from KHTML of KDE fame, and used within Safari. This seems like a much more bold decision than Google’s decision to use Webkit inside of the upcoming Android mobile operating system, considering their relationship with the Mozilla organization, but we’ll see as Chrome goes public. 

Lameness:

• The fisher price interface that is on display is really painful. Here’s hoping that when the OS X and Linux versions come out they will be substantially different. 
• Did I mention that Google launched Chrome with just Windows support? Seems a bit unnatural for Google considering most Googlers probably run a variety of Linux or OS X. 
• There are some really terrible rendering issues due to what looks like Chrome’s use of a adjusted version of Webkit. 

Overall, I’m feeling very positive about this beta release of Google’s new web browser. There are a few things that I’d love to see get fixed, but enough positive that easily makes up for the bat bits. Congratulations to the Android team, and feel free to report bugs via Chrome’s Launchpad page!