Everybody’s Human

Via Seth Godin:

First of all, before we change anything, is the light bulb really burned out? Maybe we just need to breathe some life into it; repackage it, maybe the light bulb could do a duet with somebody (Sheryl Crow? Tim McGraw?) in hopes of getting some crossover appeal, maybe it could be in a beer commercial, maybe we could get it out on the road with a brighter light bulb. … [more]

What should have been a blissful pun turned into ironic frustration as I read up on the iPhone’s event handling on the train this evening. As I navigated from one page to the next, Apple’s iPhone Developer webpages asked me to re-authenticate myself again and again. As I finished one page of documentation, and clicked to move on to the next one, Apple’s website asked me to authenticate myself. Sometimes as much as five times in a row, with no message as to why. No password mis-types. So two questions… Are cookies broken on the iPhone? Or are the sessions on the iPhone Developer pages set to expire so quickly, that they expire before my page can load, redirecting me back to the login page?

yum!

Mark Ramm, curator of the TurboGears project, wrote an interesting post claiming software development is more abstract and more concrete than natural language, making it difficult to communicate. 

Playing with the simulator for the iPhone SDK has been a lot of fun. Mobile Safari is so cute on the simulator! It’s been kinda tough figuring out how to get a sample app running on the iPhone. Here’s what I’ve found out.

To get XCode to build for the iPhone device, I had to: a) open xcode, b) open my recent project c) under the window menu, select the organizer. d) click on my iphone in the organizer and select Details from the View menu e) NOW I can use the drop down in the upper left to select “Device Debug” or “Simulator Debug.”

Even though I paid the $99 to developer.apple.com/iphone, I do not immediately have a certificate for running code on my iPhone.

This Apple link has a guide on how to request a certificate.

A developer certificate is a certificate Xcode uses to code sign your application before it uploads it to your device for testing.

To get a developer certificate:Launch Keychain Access, located in /Applications/Utilities.Choose Keychain Access > Certificate Assistant > Request a Certificate From a Certificate Authority.

In the Certificate Information window:In the User Email Address field, enter your email address.

In the Common Name field, enter your name.

In the “Request is” group, select the “Saved to disk” option.

Click Continue.

The Certificate Assistant saves a certificate signature request (CSR) file to your Desktop.

Upload your CSR file to the iPhone Dev Center.

Download your developer certificate and the Apple Root and Apple WWDR certificates from the iPhone Dev Center.

Double-click each certificate to install them on your computer.

However, I do not understand where on the iPhone dev page to upload my CSR file!

Yep, I went and dropped the $99 for it. Apparently, there will be an Enterprise Edition that a company can use to install it’s apps on it’s employees. Well, I predict that some of the good people of this world will band together and plop down the $300 and make an AppStore for the Community, bypassing Apple. This will happen if Apple takes too long to review apps. 

I’m excited. I just finished downloading it off the Pirate Bay, and now I’m giving it my first listen. I’m stoked that a high profile artist is releasing their materials under Creative Commons. (Lawrence Lessig, FTW!) In addition to the songs being released under CC, the multitracks are available, to make the Creative Commons licensing even more meaningful. I love that things like this are happening. And that the Movie industry had another record breaking box office year. Goes to show that “piracy” isn’t harming as many things as some would say.I’m on track 6 of 36. And the album gets a “Not shitty” rating. 

It’s not just fast food that’s like this. 

I found a helpful blog post on getting ssh-agent working: http://blogs.translucentcode.org/mick/archives/000230.html

After getting Mercurial built from source, make a folder for your repo.  $ mkdir ~/repo; cd ~/repo; hg initCopy the Mercurial libraries to your python install directory, or put it in your PYTHONPATH environment variable. (I also built python from source, so your command might be different.) $ cd ~/apps/apps/mercurial-0.9.5/lib/python2.5/site-packages$  cp -R hgext ~/apps/apps/Python-2.5.1/lib/python2.5/site-packages$  cp -R mercurial ~/apps/apps/Python-2.5.1/lib/python2.5/site-packages Now create a mercurial server directory somewhere. I created my mercurial server directory parallel to my repository. $mkdir ~/hgserverCopy the hgweb.cgi file from Mercurial tarfile to hgserver directory as index.cgi$ cp ~/apps/tar/mercurial-0.9.5/hgweb.cgi ~/hgserver/index.cgi$ chmod 755 ~/hgserver/index.cgi Finally, make any edits to index.cgi to point to your repository directory and to your python install’s site-packages directory.Hope that helped.