594 karma · joined August 21, 2008
$ traceroute lacehost.com
traceroute to lacehost.com (67.225.243.15), 64 hops max, 40 byte packets
...
16 209.59.157.44 (209.59.157.44) 43.978 ms 46.390 ms 43.979 ms
17 lw-dc2-sec2-dist4-po1.rtr.liquidweb.com (209.59.157.234) 45.439 ms 46.016 ms 50.775 ms
18 dc2-vps1-302.liquidweb.com (67.225.247.217) 43.915 ms 49.835 ms 46.735 ms
He probably just has a WHMap account setup on one of liquidweb.com's dedicated servers. That'll work fine, but hopefully he really is able to move you over to a private server without any snags.- system-wide keyboard shortcuts (I believe there is a Carbon API for this that you could use). It'd be great if you could hook the default Pause/Play buttons on the Macbook keyboard, not sure if this is possible
- possibly some kind of current track menu item (I wrote one for iTunes here: http://silentmac.com/?p=470 ), requires Cocoa. Just to display the current song (some of my music has long, quiet intros, and I'm not sure what song is playing in the beginning), this might go against your idea of minimalist though
- shuffle functionality
But it looks great so far!
"WARNING: 10/14/2009 The RedLaser SDK currently uses an unpublished function to access video frames. Very recently, others have indicated that this will likely lead to rejection of any application using this function, including any application with the RedLaser SDK. We are working hard to find a solution, as we believe there is great potential for this technology on the iPhone. Please take this into account when considering use of the RedLaser SDK."
So they probably analyze a lot of different video frames before finding an accurate one.
It's not that hard. There's a free app you can put on your device that will email your UDID to where ever you want, or you can just copy it over from iTunes/XCode. I haven't ever had a client give me the wrong UDID (they have given me the same UDID twice though, forgetting that I already have that device in the database). The hardest part usually is that it can sometimes take 5-6 tries of dragging the app into iTunes (on Windows at least) for it to work. But even that isn't too big of a deal, just quick and easy repetitive motion (once they get the profile installed).
I think the biggest pain in the ass is on the developer's side. Anytime you want to run the app on another device, you have to add another UDID to the device list on Apple's site, regenerate your provisioning profile, download it, delete the old adhoc profile from ~/Library/MobileDevices (good luck trying to find out which of the profiles in there is your old adhoc, the files are named with a random string of letters and numbers), install it to XCode, open your project, and change your adhoc build profile settings to the new profile.
Phew.
http://www.techcrunch.com/2009/08/01/pizza-huts-delicious-ip...
Except it is more geared at remotely ordering a pizza to be delivered.
Or the actual developer gaming the system with 5 star ratings of his own app.
http://sethgodin.typepad.com/seths_blog/2008/11/an-iphone-ap...
He nailed it.
I do get tired of bloggers disputing what should be fact by mixing it with rumors or secondary sources...
[techcrunch quote]: "The first part of Apple’s argument, that they never rejected the application, is “a total lie,” according to many sources with knowledge of the Google Voice application process." ... "There is overwhelming evidence that Apple did in fact reject the application."
[daringfireball quote]: "Google’s initial statement regarding this did not use the word rejected either. Their spokesperson told TechCrunch: “Apple did not approve the Google Voice application we submitted six weeks ago to the Apple App Store.”"
Who is trying to mislead us here? Techcrunch throws unnamed "overwhelming evidence" and unnamed "sources" at my face, while daringfireball talks about Google's "initial" statement. Was there a second or third statement that cleared things up?
Anybody have the facts?
Edit: fixed and fixed
I added a word checker, so no more of this tomfoolery!
"Oh but for your trouble I generated a few hundred thousand hashes for you. --Phil Freo"
Thanks Phil :-) Your message's hash had a hamming distance of 73