Serious uses for YouTube’s new popup video feature

June 8th, 2008 Scoop Posted in Technology No Comments »

I’m loving YouTube’s new video annotation feature, which Phil Shapiro alerted me to. Lots of people are going to have lots of fun with that. If you remember when MTV first started doing popup video, you’ll have some idea how much fun.

But from Phil’s perspective and mine, this is a seriously useful tool as well. He’s planning to annotate screencasts with it. And I found a great use for it here.

That short video features Bob Coffey, the senior climber at our YMCA. When I made and posted the video, I wasn’t quite sure how senior Bob was so I didn’t say. Yesterday I remembered to ask. Turns out he is 79.

It’s painful to add new information to a video. Opening up the raw file (if you even kept it around), adding a caption, recompressing, reuploading — it’s too much overhead, and unless there’s a compelling need you’re just not going to bother.

Of course you can update the textual wrapper, and alter the title or description. But in this case, I didn’t want to that. The information is much more effective when inserted midstream. After he’s scampered halfway up the wall, the popup annotation saying “Bob Coffey is 79 years old” makes the point more subtly and powerfully.

The point, by the way, is that we can do more, physically, at all ages, than we think. I’ve known a few people over the years who have redefined what’s possible, and it’s always an inspiring thing to see.

AddThis Social Bookmark Button

AMD shakes PC notebook status quo

June 8th, 2008 Scoop Posted in Technology No Comments »

At the logic level, MacBook, the benchmark for success in mainstream notebooks, is unremarkable — indistinguishable from every PC notebook built on Intel Core 2 and its chipset-integrated graphics. Why, then, can’t anyone with the same parts list emulate Apple’s growth in an otherwise stagnant notebook market? Because Apple painstakingly hand-optimized its OS for a tiny variety of hardware architectures, presently Intel Core 2, while Microsoft wrote Vista to run on absolutely everything. No PC notebook maker can take the proprietary route that Apple plays to such advantage. Microsoft can’t crank out proprietary cuts of Vista for each notebook vendor’s choice of suppliers. The best hope is a hardware architecture that’s optimized for Vista. Not only that, but optimized for 64-bit Vista running on a battery. That radical objective drove AMD’s design for the total notebook platform nicknamed Puma, and now dubbed, temporarily I hope, AMD’s Next Generation Notebook Platform. This platform’s Turion X2 Ultra 64 CPU is not cut from the common cloth of adapted desktop platforms like Core 2 that rely on machinations of the OS to balance performance with battery life. The combination of Turion X2 Ultra 64, AMD/ATI scalable graphics technology, AMD’s M780G bus interface, and… READ MORE

AddThis Social Bookmark Button

Questions for Exchange admins about public calendars

June 8th, 2008 Scoop Posted in Technology No Comments »

To complement my series on client-side calendar publishing, I’ve been looking for a way to push ICS files from Exchange. Why? A couple of local organizations with calendars I’d like to include in my calendar syndication project are running Exchange. It’s true that individuals within those organizations can use Outlook 2007 to publish calendars to the Internet. But companies like to manage these processes centrally. If the city wants its recreation center to publish summer activities, the city’s IT department should be able to do that whether or not the rec center’s desktop machine is alive.

Several folks suggested that the WebDAV interface to Exchange is the way to go, and after noodling on that for a while I’ve come up with a solution that seems to work. (I’ve tested it on a server here in my lab, and against my account on a production server.) I’m planning to release it as a CodePlex project, but as a Microsoft employee I have to cross a few t’s and dot a few i’s to get that done.

Meanwhile, since I’ve never administered Exchange, I have some questions for those who have. What I’ve got is a 100-line IronPython script that can be run on a scheduled basis. You give it a hostname and an account name, it reads events from that account’s calendar, and emits an ICS file.

First question: How does this fit in with your workflow? If you’re a town government, how would you like to manage your public calendar from Exchange? For example, would employees in various departments share one account that corresponds to that calendar? Would you rather divvy things up and then syndicate a set of calendars?

Second question: How will you want to publish the ICS file? My script only creates it. To publish the file to the Net, it could be copied to a directory on a webserver, or it could be uploaded to lots of places in lots of ways. It’s good to have choices, but it’s also good to have a sensible default, and I’m not sure what that should be.

Third question: Would you deploy this thing? I hope the small footprint will help. Being wary myself of solutions that haul in boatloads of requirements, I’ve whittled them down. You only need IronPython, plus of course the .NET Framework which it requires.

Originally, I was also using a few things from standard Python: command-line arguments, regular expressions. But it struck me that requiring all of standard Python for just those things was overkill, so I switched to their IronPython/.NET equivalents.

IronPython itself, resting as it does on the .NET foundation, is a tiny installation. Even so, it’ll be a new and unfamiliar thing to most people. Would an Exchange admin be willing to install IronPython on a production server and allow it to do the things this script does?

AddThis Social Bookmark Button

Relevant Links