The more closely I scrutinize Apple’s latest iPhone event invitation, the more I begin to believe that we will not actually see the SDK released next week. And it may be even longer before users have access to SDK software.

For starters, there’s the wording: “Please join us to learn about the iPhone software roadmap, including the iPhone SDK.” Why use the word “roadmap” at all? Why not simply say: “Please join us to learn about the iPhone SDK” or “Please join us for the unveiling of the iPhone SDK”?

The word “roadmap” suggests a journey. And a journey takes some time. It makes me think that we are going to learn new details about Apple’s plans for the SDK next week, rather than actually see the release of the SDK.

Then there’s the graphic image of the roadmap itself, which shows a road with markers for “Enterprise” “SDK” and “Software Update” spaced out along the way (in that order). One interpretation of this is that new Enterprise features will be made available (or even just announced) first, followed by the release of the SDK to developers (perhaps a beta version initially), followed by an iPhone software update that (finally!) allows users to obtain the SDK-dependent software.

Within such a framework, the SDK could be out within a few weeks while the Software Update may not become available for another several months.

And yes, this is all just speculation. Perhaps I am over-interpreting the tea-leaves here. A week from now, we’ll know for certain.

Apple came out with new MacBooks and MacBook Pros yesterday. Aside from the new additional features announced, there was one subtraction: The laptops no longer ship with a remote control. It’s now a $19 option.

I imagine there will be some grousing about this among users, complaining that Apple is increasingly “nickel-and-diming” us, removing default components and charging extra for them.

But let’s be fair. Apple has gone both ways. For example, an AirPort Extreme card and Bluetooth support are both standard with laptops, even though they were optional when they first arrived on the scene.

In the case of the remote control, I suspect Apple simply made a decision based on cost vs. use. That is, if the vast majority of people who purchase a Mac laptop never or rarely use the remote control, then Apple is wasting money by providing it to people who will just let it sit in a drawer. Plus, there are the people (such as myself) who now have several of these remotes (after purchasing laptops, an iMac, and an Apple TV over the past few years) and who don’t need a new one with each new purchase.

So…make it an option for those who want it and save money (by not raising the price of the laptop) for those who don’t. Compared to the status quo (keeping the remote standard while not increasing the price), an optional remote can save Apple a significant amount of cash. Let’s suppose (and I am making a wild guess here) that a remote costs Apple $10. That’s $10,000,000 saving for every million laptops it sells.

On the assumption that most users won’t miss not having the remote, or won’t mind paying $19 to get one, that’s money well saved at little or no cost in customer satisfaction. Makes sense to me.

My email today made for some amusing…as well as mildly irritating…reading with my morning coffee.

Filling up my Inbox were a collection of messages all with the same subject: “Re: Confirm.” They were all from people on Apple’s Weekly-kbase-changes mailing list, to which I subscribe.

The end of each mailing from Apple states: “Do not post admin requests to the list. They will be ignored.” Apparently, someone ignored this request and did reply, possibly in response to some deliberate hacking email that solicited replies (I’m still not exactly sure how the entire cascade got started). In any case, this led to further replies, all of which were somehow sent out to everyone on the mailing list—which is how I started getting them.

Before it ended, I had received several dozen emails. Editing out redundancy, they went something like this:

“What is with all these confirm emails?” John

“I was wondering the same thing.” Robert

“I am curious as well.” Richard

“Beats me, Apple mail list got hacked I guess.” Kerry

“I echo the same question. I think it has something to do with KBase updates … or lack thereof.” Steve

“I have received two such messages, and am at a loss to know why.” Adair

“Hmm. I think that I didn’t realize this was a public list, that anyone could post to, and a couple of folks were trying to confirm subscriptions, perhaps. My bad? I guess so. Didn’t mean to set off a storm, haha.” John

“SPAM. All on this list - PLEASE DO NOT SEND ANY REPLIES TO THE GROUP.” Scott

“Gentlemen: I got a notice regarding the weekly kbase changes. I assume that I am being sent this email to see if I wish to continue. The answer is yes I enjoy the articles very much.” Jim

“Please make the changes to prevent this from happening!!!” Greg

“Be interesting to know how many thousands around the world are receiving these emails.” Tim

“Confirm what? Please advise.” Liu

“JUST STOP REPLYING!!!” David

“Sorry guys, I do not have a clue what is going on…it feels like a Microsoft-Gates thing.” Robert

“Will you please all stop replying. Let the situation get resolved and leave it alone. Thank you.” Shane, Mac Genius

Not a big deal. I just thought that you might want to know.

Ted

P.S. Please do not confirm.

Leopard-compatible betas released!

Coincidence can be a funny thing.

Just last week, I emailed the folks at Unsanity software, requesting an interview. In case you don’t know, Unsanity makes about a dozen popular utilities for Mac OS X. By far, my favorite is WindowShade X. It has long been (together with LaunchBar) one of the first two third-party utilities I install on every new or updated Mac.

The problem has been that virtually none of the Unsanity haxies (as most of their utilities are called) have been updated for Leopard—even though Leopard has now been out for about four months and just about every developer who intends to come out with a Leopard update has already done so. Making matters worse, Unsanity has not exactly been forthcoming in explaining the reason for the delay or when it might be over.

In a blog entry from last October, Unsanity stated, “We have a build internally that works with Mac OS X 10.5… so it’s a matter of days for the compatibility update.” Unfortunately, the promised update did not appear in the next few days…or weeks…or months. Queries from users—as to what was happening—were met with silence. No further blog entries on the subject were posted. Postings from users began getting increasingly cranky and critical.

It was this backdrop that led to my request for an interview. I hoped they might be willing to sit down for a talk and explain what was going on.

Therein lies the coincidence. I received a reply from Unsanity today, politely declining my request for an interview. Instead, I was directed to a pair of blog entries, posted yesterday, for the answers to my questions: Pragmatic Disillusionment and Enthusiastic Trepidation. I don’t flatter myself to imagine that my email triggered the blog entries. As I said, I am sure the timing was just a coincidence.

Still, the entries do provide most of the answers I would have sought.

The main thing is that they announce the release of Leopard-compatible beta versions of much of Unsanity’s software. I quickly installed the beta version of WindowShade and — yea! — it works.

[Two troubleshooting notes: (1) Although the installer says that you can either log out or restart to get the software to work, I found that a restart was needed to get the essential Application Enhancer (APE) component to run; (2) After installing the new version of APE, any haxies that are not specifically recognized as compatible with Leopard will be disabled automatically. This includes haxies not made by Unsanity.]

When will these still not 100% complete beta versions be replaced by final released versions? When, if ever, will new versions of Unsanity’s remaining software be released? Don’t ask. Literally. All Unsanity will tell you is that “it’ll be done when it’s done.” Unsanity adds that any more precise ETA is likely to be wrong and so they won’t provide one. If you post comments requesting an ETA, they will be edited or deleted. At least Unsanity offers an apology for the delay in getting these two blog entries (and updated programs) posted, with health problems cited as a primary cause.

Most of the technical details in the remainder of the blog entries are directed at developers. Still, there are several nuggets of more general interest to be found.

The first blog entry (Pragmatic Disillusionment) is entirely devoted to explaining why the existing release versions of Unsanity programs do not work with Leopard. Although this has some bearing on what gets covered in the next entry, there really isn’t much value, in my view, in slogging through the details of why haxies and Leopard have not played well together.

The second blog entry starts off by similarly staying in the past. It offers a very lengthy defense for why a version of Application Enhancer may cause a blue screen crash at startup in Leopard (as described here). Noting that it only happened if you were using an out-of-date 2.0.1 version of APE, a version that was updated more than a year before, the blog entry expresses indignation toward people who asked the “loaded question”: “Why didn’t you test APE 2.0.1 before Leopard was released?” The entry goes on to add that it would have been impossible to test the older version anyway, as the final build of Leopard (which revealed the bug) was not available to developers until the same time it was released to the public.

So, no, Unsanity is not apologizing for any problems caused by APE under Leopard.

At last, the blog entry moves to the present and provides links to the current Leopard-compatible beta versions of its software.

And that’s all you are going to get from Unsanity, until they are ready to tell you more. Whenever that is.

P.S. The blog entries, in addition to discussing the status of Unsanity’s software, contain several intriguing troubleshooting tidbits.

Most notably, they provide explanations for blue-screen freezes/crashes at startup that have nothing to do with any Unsanity software. For example:

The blog entries also point out, at least twice, that InputManager software must not be installed in the user’s home folder (~/Library/InputManagers) in Leopard, as it will “prevent the InputManager from loading even if the InputManager is installed globally in /Library/InputManagers and meets all the requirements to load.” In other words, check your ~/Library/InputManagers folder. If you find anything there, remove it. Doing this at least offers a chance for other InputManager-dependent software to work. While most Unsanity Software does not use the InputManager, two do: Smart Crash Reports and Menu Extra Enabler. These will now install in /Library/InputManagers.

The HD-DVD format is dead. Toshiba made it official the other day, “conceding defeat to the competing Blu-ray technology backed by Sony.” With retailers dropping the format from their stores and studios opting out of releasing movies in HD-DVD, Toshiba had little choice.

For Sony, it can afford to breathe a welcome sigh of relief. They dodged a bullet and avoided going 0-2 in media format wars (its Beta format lost out to VHS in the previous round). But they can’t afford to relax too long. Blu-ray may be the victor here, but Sony may ultimately not have much to celebrate.

For starters, I doubt there will be a sudden upsurge in sales of Blu-ray DVD players. Most users will be content, for now, with their current DVD players. Only when the price of a Blu-ray player begins to approach what standard definition players cost today (under $100) is that likely to change.

On a related front: When I shifted from videotape to DVDs, I wound up repurchasing many of the movies I already owned in VHS. Doing so was worth it because the quality of the display and sound was so much better with DVDs. It was also a huge convenience to be able to skip almost instantly to any part of a movie (and not have to worry about rewinding). The added features that came with DVDs (such as deleted scenes and commentary tracks) were a bonus, although not critical ones for me.

I don’t expect to make a similar conversion to Blu-ray, even after I buy a Blu-ray player. First, many older movies will never be released in a true HD-quality version, because such quality will not be possible. Second, the improvement of the HD version over a standard DVD version is not enough to make it worth the cost (at least to me) of purchasing a second (or even third) version of the same movie. If studios had some trade-in policy (where you get a discounted version of a Blu-ray DVD by trading in your old standard DVD), I might be inclined to bite, but I don’t see this happening.

But all of this may well be moot. The DVD format, Blu-ray or otherwise, could be dead (or at least on life-support) before too long. It will take a few years, but it’s coming. Downloading movies is what will slay the DVD. The specifics are still a bit unclear, but my crystal ball sees a mash-up of the Rhapsody music service, the iTunes Store, Apple TV, and Netflix. Let’s call it TedFlix. I see it working something like this:

TedFlix will have a library that includes almost every film currently available (much like what the iTunes Store is today for music). Where an HD version of a movie exists, TedFlix will have both HD and standard definition versions of the movies. The HD version will be true 1080p. With devices similar to Apple TVs (let’s call them Ted TVs), you will be able to download the movie directly to your TV. With just slightly improved download speeds, you should be able to start watching the movie almost immediately after you click to rent it.

The rental period will be 72 hours. Further, you will be able to rent up to a maximum of three movies in any 24 hour period and up to a maximum of 60 movies a month. The cost? A monthly subscription fee of $24.95 (perhaps less if economics allow).

TedFlix, if successful, would effectively kill off most of the demand for Blu-ray discs, as well as the DVD rental business. There will likely be some market remaining for retail purchases of DVD packages (such as to give one as a gift). But the demand will be small.

Still, there may be a place where Blu-ray could survive, even thrive: Blu-ray DVD burners. Let’s include such a burner as part of each Ted TV unit. Why? Well, what if you want to watch all those “extras” that come on a purchased DVD, instead of just watching the movie? Or what if you want to be able to play a movie on a television other than the one to which your Ted TV is connected? Not a problem.

With TedFlix, you can optionally select to download and burn a complete DVD, an exact duplicate of what you would otherwise buy in a store. I foresee two variations here. In one case, the burned DVD only plays for 72 hours, and probably only plays on “authorized” devices (similar to how iTunes now works for purchased music). You pay a small fee (say $1.00) for each DVD that you choose to download and burn in this way. In the other case, you purchase the burned DVD (for a competitive price). It’s now yours forever and has no authorization restrictions. However, just as with a purchased DVD, you won’t be able to make copies of it. Admittedly, given the size capacity of Blu-ray DVDs, these burns may be impractical to do at current download speeds, but much faster connections are not too far off.

What about transferring movies to iPods and iPhones? I don’t quite have this worked out yet. But a model for doing this already exists in the iTunes Store; I am sure it can be adapted to work in TedFlix.

With TedFlix and Ted TV, you will be able to watch any movie you want, whenever you want—for just one monthly fee. Want to watch a movie for a second time, months after you first watched it? Just select it again. There’s no additional cost. And if movie technology improves, you’ll get the benefit of it, without having to repurchase your DVD library.

This may not be the future that Sony or the movie studios would prefer, but I doubt that will stop the train. I think I already hear the whistle in the distance. I certainly hope so.

Update: After writing this, I noticed that David Pogue also posted a column today on this topic. He takes a much more pessimistic view of downloaded movies. I don’t disagree with his assessment. However, he is talking about the present. I am talking about a hopeful future.

The HP-11C and HP-15C calculators are, quite simply, the best single-line display calculators ever created. If you don’t absolutely need a graphing calculator, they remain the best handheld calculators ever…period. This is true despite the fact that they date back to the 1980s. These HP marvels came with a sumptuous array of built-in functions together with a simple yet powerful method for programming (which allowed you to expand way beyond its built-in features). They also sported a sleek thin design that still surpasses any of the calculators on the market today. Best-of-all, they used RPN (Reverse Polish Notation) for data entry.

RPN, for those of you unfamiliar with this odd-named duck, is the alternative to the algebraic method of data entry. The algebraic method is found on virtually all other competing calculators (most notably the ubiquitous handhelds from Texas Instruments). You know you’re working with RPN if you use an Enter key instead of an Equals (=) key. Of course, the differences go beyond that simple distinction. Skipping over details, let me just say that, for anything beyond the most simple calculations, RPN is much easier to use, easier to keep track of what you’ve entered, and less prone to making mistakes. If you have ever been frustrated by entering a complex expression involving parentheses, for example, RPN will seem like a direct delivery from heaven.

Unfortunately, RPN lost out in the calculator wars. Even Hewlett-Packard largely abandonned it. They still make the HP-12C (a financial real estate calculator variation of the 11C). Beyond that, their calculators have either shifted to algebraic-only or a combined algebraic-RPN system. I am sure the reason for this is that, at first glance, RPN seems quirky and hard-to-learn. Admittedly, it does have a slightly steeper learning curve than algebraic entry. But once you make the minor effort to get over the hump, you are more than rewarded for your efforts. It may not seem like it at first, but RPN’s “inside-out” method of working through an expression mimics the way you would do such calculations in your head—much more so than the algebraic method.

I still use my trusty HP-15C. However, I must admit that it spends most of its time in a drawer of my desk. That’s because I now do almost all of my calculating on a Mac, via spreadsheets and such. And if I do want an HP-15C while working with my Mac, I simply launch a nifty emulation that’s almost as good as the real thing. The only remaining advantage of the “real” 15C is its portability.

This (finally) brings me to the main point of this blog entry. Last week, I was browsing through the list of programs available for my hacked iPhone (as viewed from the Installer utility) and discovered a set of HP calculator emulations (11C, 12C, 15C and 16C). I installed the 15C. It’s fantastic! After launching it, the phone becomes an HP-15C. The entire display is filled with an exact image of the calculator. To use it, you just tap the virtual buttons. The net effect is almost identical to pressing the physical buttons on an actual HP-15C. If you ever want to show off the advantages of a touchscreen interface, you’d be hard pressed to find a better example!

In a sense, I now have my HP-15C back in my pocket again. Actually, it’s even better. My “new” 15C doesn’t have to compete for space with my iPhone. The iPhone is the 15C. Ahhh…the joys of the iPhone…and iPhone hacks!

I only hope that, after the iPhone SDK is released in a few days, the HP-15C is one of the third-party programs that will be “officially” available, so I won’t need a hack to get it.

In my previous blog entry, I described the three features I liked best in the new Apple TV “Take Two.” A couple of reader comments made reference to a new feature in Take Two that was not on my list. In fact, I had not realized the feature was even there at first: the ability to use AirTunes to play iTunes content on an audio system connected to an Apple TV.

This is indeed a great new feature. So much so, that I decided to cover it here as a follow-up to my previous entry. As to why I didn’t notice the new feature in the first place—after accepting responsibility for failing to look closely enough—I would add that Apple has hardly promoted this new feature. In fact, if you go to the Apple page that lists the new features of Apple TV Take Two, the word “AirTunes” is not even mentioned. I could similarly find only one Apple support document that acknowledges its existence.

Complicating matters further, for many users, it will not be immediately obvious what this new feature adds. Apple TV “Take One” owners are already familiar with streaming iTunes content from a secondary shared computer (not the one that is synced to the Apple TV). Take Two continues to do so. The Take One version of Apple TV could stream movies and TV shows from a Mac. That’s not new either.

So what is new with AirTunes support? It provides the ability to stream any audio content in your iTunes Library to your Apple TV, even if it is not in a playlist. Actually, with AirTunes, you can stream audio content from any computer on the same network as the Apple TV, even if it is not a Mac being shared or synced with your Apple TV! Not only can you play all your music from your Library via this method, but you can play Audible content or Internet radio stations as well!

To do all this, just enable the connection via the same method that is used to connect a Mac to the AirTunes feature of an AirPort Express: At the bottom of the iTunes window on your Mac, access the Computer pop-up menu and select the name of your Apple TV. Next, select an item to play. Done. There is no setting on the Apple TV itself that needs to be enabled or selected. [Well, that’s not 100% true. There is an Apple TV setting to enable AirTunes, located in Settings > Audio. However, it is on by default.]

You can use your Apple TV remote to pause/play or skip items. If your Apple TV doesn’t respond to your remote here, you need to enable the necessary preferences item in iTunes: Go to iTunes’ Preferences and select Advanced > General. From here, make sure the AirTunes option to “Allow iTunes control from remote speakers” is enabled.

The key thing to remember in setting all of this up is that, unlike other Apple TV connections, you do not make the connection or select the music to be played from the Apple TV itself. Instead, you do it from iTunes on your Mac (again, the same way as if you were connecting to an AirPort Express rather than an Apple TV).

Note: If iTunes is open on the Mac that is synced to your Apple TV, you automatically have access to most content in your iTunes Library, via streaming, even without using AirTunes. Just make sure that the option to “Show only the synced items on my Apple TV,” in the Apple TV Summary pane, is not enabled. There is no longer a separate listing for synced vs. streamed content, as in Take One. This is just one more of the many differences between Take One and Take Two in the areas of streaming, sharing and syncing—most of them still not documented well (if at all) by Apple. Apple has some work to do here!

The AirTunes feature is apparently still a bit rough around the edges, as I have seen several reports of problems with it getting it to work. I have had one of these problems myself. When playing audio via AirTunes, if you select Music > My Music > Now Playing on your Apple TV, you should see the name and artist of the currently playing song. I don’t. Instead, all I see is “untitled” and “unknown.” I haven’t yet figured out why some users have this problem and others do not—or how to fix it. But I am working on it (I did see one report that said a “factory restore” of my Apple TV would fix this; I haven’t tried this as yet and am reluctant to do so). It is almost certainly an issue with the Apple TV rather than the Mac, as I have the same symptom no matter what Mac I use.

{revised slightly on 2/17/08}

Apple TV “Take Two” is definitely worth the upgrade. It so transforms your old Apple TV, it is almost as if you sold the old model and purchased a new one. And it’s free. There’s virtually no downside here.

Among all the new features in Take Two, I already have three favorites:

Podcasts. This is my #1 favorite new feature. While there are many podcasts that I would enjoy listening to, I rarely do—because I rarely want to take the time to sit down and listen for an extended time. With Apple TV Take Two, however, I can easily listen to podcasts from my living room TV, allowing me to (for example) prepare and eat dinner while the podcast plays in the background.

True, I could play a podcast from my iTunes Library even with the old Apple TV. But the new version makes it so much more convenient. I don’t have to subscribe to a podcast or worry whether the one I want to listen to is on my Mac or not, or synced to my Apple TV or not. I just directly start browsing podcasts on the Apple TV and play the one I want. As a bonus, you can play it without having to download it. This means that, once you are done listening, you don’t even have to remember to delete it from the Apple TV (assuming you don’t care to save it, as will usually be the case). The process is as simple to do as it is to select a broadcast TV channel to watch.

Some users have complained that you cannot subscribe to a podcast from the Apple TV. Personally, I don’t see this as a negative. If I really want a subscription, I can still do it from my Mac.

.Mac and flickr photos. I had already been using Apple TV “Take One” to displays photos from my iPhoto Library. With Take Two, I can now play slide shows from .Mac Web Gallery and Flickr accounts. This doesn’t add much value for playing my own photos at home (it’s just as easy to use my iPhoto Library directly for that). But it’s a great way to view other people’s photos—or even to show your own photos when you are at someone else’s house (if that someone else has an Apple TV and is willing to put up with watching your vacation slideshow!).

HD content. You can rent HD movies directly from your Apple-TV connected television. Unless you already own a Blu-Ray or HD-DVD player, and prefer having physical discs, Apple TV is currently the best way to rent HD content for your television. With “Take Two,” you can even play theatrical movie trailers in HD. Very cool!

I do have one relatively minor complaint with “Take Two”: All the menus are organized around iTunes Store content. This means, for example, if you want to play music from the iTunes Library on your Mac, you first have to select “Music” from the main menu and then (from a submenu that lists Top Music, Music Videos, Genre, Search and My Music) select the last choice (My Music). This finally takes you to the menu for your iTunes Library; a menu that looks pretty much as it did in “Take One.” The net effect, however, is to make you feel as if your own music is semi-buried amid the iTunes Store options, as if Apple TV is now designed primarily as a device to sell iTunes content (and maybe it is).

On the other hand, as a music video fan, I welcome how easy it is now to browse through and purchase music videos directly from the Apple TV. If you purchase a music video (or any item, other than a rented movie), it is transferred to the iTunes Library on your Mac, automatically, the next time you sync your Apple TV.

One caution: I have my Apple TV connected via a 802.11n connection. I am not sure how much streaming and downloading would be negatively impacted by a slower 802.11g connection.

I am still happily using iPhone software 1.1.1—even though 1.1.3 is the current version and includes some cool new features, such as Maps “My Location.” Why am I still stuck at 1.1.1? Because I don’t want to abandon all the third-party software I’ve installed, software that I was able to put on my iPhone only after “hacking” or “jailbreaking” the device.

Now before you start posting comments, I am fully aware that there are reportedly ways to successfully hack 1.1.3. I could apparently have my cake and eat it too.

Thanks, but I prefer to save the calories and pass. The biggest reason should be no surprise. Apple will be releasing its iPhone SDK (Software Development Kit) later this month. This will, finally, provide an Apple-supported method for adding third-party software.

I have some hope that the SDK will wipe out any need to hack the iPhone. But I am not betting on it. I suspect that Apple will maintain at least a degree of control over what you are permitted to install. For those who want software not on Apple’s “approved” list, jailbreaking will remain the alternative. When that happens, I’ll reconsider my options.

But even if the SDK wasn’t coming, I’d likely defer on updating my iPhone. For now, I don’t see any point in taking even a small risk on the current jailbreaks.

And, to be clear, jailbreaking 1.1.3 carries some very definite risks. Depending upon which method you choose and your current iPhone setup, jailbreaking may: (1) simply fail to work and could require that you restore your iPhone with possible loss of data; (2) break certain iPhone features (including the very My Location feature that would be my prime reason for updating); (3) prevent SDK-supported software, when it becomes available, from working (unless you “undo” the jailbreak).

If that’s not enough to keep “jailbreaking” off the table for you, consider that the current methods are not exactly a piece of cake to install. For starters, in almost all cases, if you are already running 1.1.3, you’ll have to downgrade to 1.1.2 or even 1.1.1, before you can get the jailbreak to work. This is a multi-step process in itself, and not for the cautious Mac user. In any case, finding clear well-written instructions can be more difficult than actually doing the install. Gone are the days of the one-step Web-based process that worked with 1.1.1.

Finally, there is the deal-breaker for me: there is no clear consensus on the best way to jailbreak. From the perspective of an “outsider” to the hacking community, it looks like a confusing mess. I suspect it may seem that way even to those in the know.

The first publicly released hack for 1.1.3 was posted by Nate True around January 24. Nate was a member of the the iPhone Dev Team (a group responsible for most of the iPhone jailbreaking methods). However, the Team claimed that Nate’s method made use of material copyrighted by Apple and was thus potentially illegal (my guess is that Apple views all jailbreaking methods as having questionable legality, but that’s another story). Anyway, as a result of this breach, Nate was apparently “kicked off” the Dev Team.

A few days later, the iPhone Dev Team released its own 1.1.3 jailbreak. But don’t get too excited. The team pointed out, that this was not their “true” jailbreak method. Rather, this was a stopgap “soft-upgrade” method. The true method, when released, would be superior, with none of the potential problems of the stopgap method.

So why not just release the true method right away? If only things were that simple. The true method was being kept secret. Why? The logic was to wait until after Apple released the SDK, thereby preventing Apple from including a block to the true method in its next SDK-supported update to the iPhone software. This logic presumes that Apple remains unaware of the true method and would work to stop the jailbreak if it could. Plausible assumptions, but by no means certain.

Meanwhile, an update to a program called iJailBreak—and its iJailBreakMobile cousin—arrived on the scene. These utilities offered yet another way of jailbreaking your iPhone. The Mobile utility had the advantage of being able to jailbreak 1.1.3 directly from the iPhone, freeing the process of any dependence on a computer. However, it only worked if you were already running a jailbroken iPhone running 1.1.2 or 1.1.1, so you still would have work to do before you can use this utility. As I understand it, and I admit to have some trouble following all the soap-opera twists-and-turns here, these utilities are not a product of the iPhone Dev Team.

In quick response, the iPhone Dev Team released its own “computer-free” method for jailbreaking 1.1.3. It was labelled the “Official 1.1.3 Upgrader” (as if there really is anything official about any of these methods!) and you accessed it via the Installer utility on a jailbroken iPhone.

Hot on the heels of the Upgrader, a developer named Zibri released ZiPhone. As stated on the iPhone Atlas Web site, this software “claims to jailbreak, activate and unlock all iPhones running software/firmware 1.1.3 (including out-of-the-box) devices. The ZiPhonepackage uses the ‘true’ jailbreak method that the iPhone dev team was attempting to keep secret until the release of Apple’s official SDK…” However, it is not a product of the Dev Team—and I have seen no “official” confirmation of its “trueness.”

For what it’s worth, as of yesterday, I couldn’t even get the ZiPhone package zip file to decompress on my Mac. It hardly seemed to matter, at least for Mac users, because Zebri’s blog states that the Mac OS X version no longer works (assuming it ever did). I downloaded an apparently new version today. It did decompress, but it is still not clear that it can successfully jailbreak an iPhone.

For those of you who are still following all this, iJailBreak 0.5.1 was released yesterday. The unique claim of this latest version is that it can jailbreak an iPhone running 1.1.3—no need to downgrade to an earlier firmware version. However, it does not yet support the iPod touch, only an iPhone. It is apparently based on the ZiPhone method.

So where do things stand now? Well, you can choose among illegal methods, official methods, secret methods, true methods, false methods(?), computer-free methods, methods that don’t really work, and on and on. If you want to venture into this world, fully aware of all the risks and hassles, do so. But for anyone with the least bit of reluctance, I recommend staying away—at least until after the SDK comes out and hopefully after the hacking community cleans up their act, gets their house in order, and comes up with an agreed-upon reliable method for jailbreaking.

When you rent a movie via the iTunes Store, you have 24 hours from the time you start watching the movie until it is erased from your drive. That’s marginally better than the situation with Comcast (my cable provider). With Comcast, the 24 hour clock starts ticking from the moment I rent a movie, whether I start watching it immediately or not—making me feel a bit like Jack Bauer in 24. With the iTunes Store, you have a generous 30 days within which to start watching the movie.

The problem for me, even with iTunes Store rentals, is that I often want to watch a movie over two nights. The 24 hour limit gets in the way here. If I start watching at about the same time each night, I won’t get to see the second half of the movie—because I will have exceeded the time limit. A 36 (or even a 30) hour rental would make so much more sense. I know I am not alone here. A recent column by David Pogue makes the same point.

This is one reason I never rent movies from Comcast. It’s also a reason why I have been reluctant to try rented movies from the iTunes Store. Still, I downloaded one the other day, primarily as research for an article I was writing.

With the movie now on my drive, I naturally began to wonder exactly how strictly the 24 hour limit was enforced.

It turns out that it’s not enforced all that much.

What did I do? The most obvious thing I could think of. I changed the time. More specifically, after starting to watch the movie and putting the 24 hour countdown in motion, I went to the Date & Time System Preferences pane. From here, I unchecked the option to set the time automatically. Then I pushed the clock back a day.

Sure enough, iTunes now said that the movie had an extra day remaining before it expired. I still wasn’t sure that this would have the desired effect. But it did. The 24 hour period passed and the movie continued to play.

With success coming this easy, I figured I couldn’t be the first person to have come up with the idea. I was right. When I did a Google search, I found several similar reports.

There are couple of hiccups that can occur if you start pushing times around. iTunes may get a sense that something is a bit off. Occasionally, especially after changing the display size via iTunes’ View menu, the movie window may go gray or the sound may stop playing. Often, just closing and reopening the movie a couple of times will get things working again. As a last resort, I found that if I quit iTunes and reset the clock to less than 4 hours from the expiration time, the movie would always work fine when I relaunched iTunes.

I’ve made no attempt to see whether the extended time limit would hold if I transferred a movie to an iPod or an iPhone. I see possible complications here, as these devices have their own clocks. But I leave that for someone else to worry about.

In any case, I imagine that Apple will eventually find a way to prevent these time extensions from working. But who knows? Apple at first tried to block iPhone users from creating their own ringtones for free. In a 180 degree turn-around, Apple later not only ended the blockade but offered tools for creating ringtones using GarageBand.