I just made the official announcement over at Smart Goat, but I also wanted to get into some of the whys and wherefores of the whole thing.

Continue reading “Start All Over Again”…

Gruber’s been writing about the rumors of Flash coming to iPhone. I think he’s right that it’s unlikely, but I think there’s an angle he misses here:

Lastly, perhaps you might be thinking that although Flash-for-the-iPhone may not be in Apple’s interest, it is in Adobe’s — and so perhaps Adobe will port it themselves once the imminent iPhone SDK ships. Think again. The iPhone SDK is not going to be the sort of environment like Mac OS X where developers are free to create system-level plugins. No one is going to get to diddle with MobileSafari without Apple’s approval.

Gruber’s probably right, but Adobe may be able to make an end-run around this problem by porting Adobe Air to the iPhone. They’ve made it clear since the early releases that as soon as they can create mobile versions of Air (sometime after 1.0), they will. With Mobile Air they could release their own Webkit-based, Flash-enabled browser.

Of course, don’t expect this any time soon. Adobe Air 1.0 hasn’t been released yet, and a Mobile Air would likely have even worse memory issues than a MobileSafari Flash plugin. Still, I’m sure Adobe’s working on it.

One of the reasons I went ahead and upgraded to MT 4.1 is that I wanted to try the new Action Streams plugin. It’s a life stream with a lot of options for publishing what you do online. One word of warning: If you’re using the never-publicly-released MT Elsewhere plugin, disable it. Action Streams is basically Elsewhere 2.0, and the two do not play well together.

Another problem is the code in the example Action Stream widget that comes with it is not correct. I’m guessing it’s using tags from a previous version. I’ve uploaded a corrected version if you need it:

author-action-stream.mtml

However, I don’t really recommend using this as a widget, exactly. Something like this, that’s going to get rebuilt often and used on multiple pages, is best setup as an index template. Then, you can create a widget that includes it via PHP, SSI, etc.

Beyond that, though, I like the plugin. Looks fairly easy to modify, too, if you want to change how it displays actions or add services it doesn’t yet support.