Category Archives: Tools

What I need is the “Brain-To-Blog” interface!

braintoblog.jpgAs I see in the Twitter stream, many good friends of mine are attending and speaking at Blog World Expo right now out in Las Vegas. I’m not there, nor was I at last year’s BWE, but I was a huge fan of and attendee at the “Podcast and New Media Expos” that proceeded it. There are some REALLY great sessions going on out there right now.

The one thing I don’t see being discussed there is this:

I need a Brain -> Blog interface!

I need something that can take all the article ideas in my brain and just mystically make them appear on my various blogs. My problem is not a lack of ideas. No way! I have the opposite problem.

Every day I wake up with my head exploding with stories to be told … and every night I find myself going to bed with so many of those stories left untold.

I have an article queue miles long… and I find myself thinking through stories at all sorts of times… but finding the time to actually write and post those stories is so incredibly difficult. Between crazy work hours, a family I love to be with (including an extremely cute but demanding 5-month-old) and, well, the need to sleep and eat… the time to convert those articles from thoughts in the brain to words on a blog site seems incredibly hard to get.

I want the interface that’s in many cyberpunk/sci-fi stories… where I can just think the text that I want to post and… ta da.. it magically gets created! Sadly, such things are right now only in stories and research labs… but it sure would be nice to have.

Meanwhile, back in the reality of 2009, I guess I’ll just have to figure out how to carve out some more time… 😉


If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or identi.ca.


Today’s launch of Google Wave – some links and initial thoughts

googlewavepreview.jpgUnless you were under a rock, or are not in the tech part of the online world, you knew that yesterday into today was “the big day” when Google Wave launched it’s wider public preview. Having had a Wave login since back in July, but not honestly had a whole lot of folks to try it out with, I was pleased to get the invite this morning to join in the public preview. If you are in the world of Wave, I can be found at:

danyorkLPG@gmail.com danyorkLPG@googlewave.com

Feel free to invite me to a wave. [UPDATE: It appears that within Wave, you have to use the “@googlewave.com” address.]

LINKS, LINKS AND MORE LINKS…

There were, of course, a zillion stories written over the past couple of days related to Google Wave. Some of the ones I found most useful in understanding the basics:

Mashable has also had extensive coverage over the past few months, as has RWW in particular.

There were some other posts I found interesting:

The Salesforce.com demo, in particular, was quite compelling and intriguing to see how Google Wave could fit into existing business apps like Salesforce.

With ANY service that was so incredibly hyped as Wave, there was the inevitable backlash… predicted by a TechCrunch article, chronicled by a RWW piece and certainly given the greatest roasting by none other than Robert Scoble himself:

Many, many, many more posts out there, naturally, and I’m sure many more will come in the days and weeks ahead as more people try it out. (I would also be remiss if I didn’t point out Dion Hinchcliffe’s great post from back in May: “The enterprise implications of Google Wave – Definitely worth a read.)

SOME INITIAL THOUGHTS

As I worked with the public preview today, I did have some initial thoughts:

  • Overall, I definitely LIKE it – Having worked with it for a while, I have to say that the potential for near-real-time collaboration is pretty amazing. It’s great to see the ecosystem of applications (gadgets and robots) developing. The preview seems pretty fast and stable. And it’s all built on XMPP and other open standards with the promise of a distributed architecture. All in all pretty impressive.
  • UI takes some getting used to – Having said that, the user interface to Google Wave does take some getting used to. Just the way comments are inserted… it’s part IM… part email… part wiki. You might be leaving a comment toward the bottom of a wave when someone else inserts something toward the top. Just takes a bit to understand.
  • Namespace shared with GMail – This is either a good thing if you have a GMail name you like, or an annoying thing if you were hoping to get a particular name. In my case, I had perhaps naively hoped that maybe I could get “danyork”, but since someone else has that for GMail already, I couldn’t. So I wound up using my GMail account name. To be honest, it makes sense for Google to do it this way. There will just be namespace collisions for people like me with common names. So it goes.
  • Yet another place to check for messages – Both Louis Gray and Robert Scoble mentioned this, and I definitely agree… your Google Wave inbox becomes yet another place to check for messages. I already have a work email account, a personal email account (well, several, but all coming into one client), a Skype IM account, a dozen other IM accounts aggregated into Adium… so in addition to checking all of those I need to check my Wave inbox. And because it is web-based I don’t have a way in my Mac’s Dock area to know there are new messages. Hopefully at some point it will be integrated with GMail or provide some other way to help us with this issue.
  • Distributed architecture isn’t there yet – I realize that this is only a “preview” for 100,000 people, but I’m impatiently interested to see the distributed architecture outlined at Waveprotocol.org. As I recently wrote about at great length, the “Internet Way” is to have distributed, decentralized architectures. Services like email or the web where: 1) anyone can set up their own server; and 2) you don’t have to ask anyone for permission to do so. Google Wave holds out the promise of giving us a very rich collaboration infrastructure built on a distributed, decentralized model. I want to get there. Today. 🙂

Those were some initial thoughts… I’m sure I’ll have more as time goes on and I’ll write about them here.

What do you think? If you are in the initial preview pool, what has your experience been?


If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or identi.ca.


Tomorrow is “Google Wave Day” – some links to learn more…

If you’re in the tech part of the blogosphere, you are probably aware that tomorrow Google will send out 100,000+ invites to Google Wave. It’s a big deal, really, as a larger audience gets a view into what Wave is all about. Thankfully the folks at RWW put together a great post:

For those wanting the “official” Google perspective, here you go:

Now if only I could remember my %#$#% password to get into my Wave sandbox account, I could find out tomorrow how to get set up in the “real” Google Wave.

I’m looking forward to seeing Wave in action with a larger audience!

Creating an Attention Wave – Building a Package Around Your News Release

So you have some news you want to get out there. You are thinking of issuing the standard old news release… Yet in the era of the “real-time web”, when new stories are found through services like Twitter, Facebook, and FriendFeed; when the ranks of formal journalists are shrinking and the ranks of online writers are growing – and the pressure to publish is greater than ever; when there are thousands upon thousands of stories coming out each day… in all of that mess…

how do you get people to pay attention to your news?

Today, in late 2009, I’ve seen many of us in the PR and marketing space sending out more than a news release… creating a “package” of related stories in multiple media. As I’ve tried to explain this method to other people, I have recently found it useful to talk about this in terms of aiming to create an “Attention Wave”. Let me explain – and I’d love to hear your thoughts on whether this framework helps in explaining what it is we aim to do.

THE GOAL

Ultimately, of course, you want customers to read about your news and buy more of your services, products, widgets, etc. or promote your cause, goal, etc. Naturally for them to read about your news, you need to get people to write about your news.

Can you do this with a single news release?

Unless you are Apple announcing their latest sexy gadget – or Google announcing their latest free service, the answer is almost certainly… no. The reality is that journalists, bloggers and everyone else writing online are inundated with a zillion stories every hour of every day. And they are scanning those endless headlines through Twitter, FriendFeed, RSS readers, email inboxes, search results and other aggregation means.

You have one… maybe two seconds to get their attention and have them open your content.

That’s it.

Naturally, you need solid headlines that catch their attention and make them want to follow the link to read your content… but that’s the subject of another post.

What I am talking about here is assembling a “package” of content centered around your news release that hits the web in one wave… multiple stories, some from you and some from others, cascading through the “real-time web”, followed ideally by retweets and other redistribution / re-posting so that journalists and those writing online have multiple opportunities to see your content – and potentially will investigate for no other reason than that they are seeing many mentions of it.

The goal is to lengthen the time of exposure of your story to journalists, bloggers and anyone else writing.

Instead of 1 or 2 seconds while a writer is scanning new headlines, maybe you get 10 or 20 seconds… maybe a couple of minutes as stories appear and are redistributed… maybe more… maybe significantly more.

TODAY’S FUNDAMENTAL DIFFERENCE

Nothing I’ve said so far is really different from “PR 101”. It’s always been the goal of PR to earn coverage of your news. We’ve always done pre-announcement briefings with the goal of getting people to cover you and come out with stories around the time of your news release.

The difference in our new world of social media is this:

The opportunity has never been greater to tell your story in your own words.

I’m talking about more than just the social media release, although that may be one of the communication tools you use in your overall package.

I’m NOT talking about creating a series of Twitter accounts to spam Twitter… or generating bogus stories on bogus web sites linking to your content. Those are games played by people who usually lack a story to tell – and in this world of transparency you will probably be called out on doing that. I’m also NOT talking about getting listed on TechMeme, Digg, or whatever the major news aggregation site may be for your industry – that may be an outcome of your work… but I’m talking about before you get to that.

You. Sitting at your computer. Putting together a package around your news. Aiming to generate a wave of attention focused on your news.

THE MAJOR CAVEAT

First, before I go further, there is of course one major caveat:

YOU MUST HAVE A STORY WORTH TELLING!

No amount of packaging can really help a worthless story. People now have a pretty high B.S.-detector. You might succeed in getting your story a bit more attention – but the backlash might also not be to your liking.

Let’s assume you have a decent story to tell…

PACKAGE COMPONENTS

The pieces of your overall “package” will obviously vary according to your industry, your specific announcement, etc., but would typically include items such as:

  • a formal news release, including components targeted at making it easier for people to tell your story:
    • company/organization logos
    • pictures of the executives or others quoted in the news release
    • pictures of the product, or visually interesting screenshots
    • links to a video and other components of your package

  • a post on your corporate blog (you have one, right?), “humanizing” the more formal language of your news release and explaining the release in a more conversational tone
  • one or more embeddable videos, posted to your blog site or YouTube channel, providing a video interview, a demonstration, or other content. This could be multiple videos… perhaps one an interview with someone quoted in the news release going into more detail and a second providing more of a demo of the product. They need to have “embed codes” that allow writers to embed the video directly into their blog or news site.
  • a “deeper dive” post that goes into more detail around whatever was announced. Ideally with some interesting diagrams or other images that could be incorporated into other posts. Potentially, depending upon your industry, some sample apps or source code or items that others can try out.
  • companion posts on company/employee blogs: if you have other blogs for your company, perhaps targeted at specific audiences, can you plan a post related to your news that is relevant to that audience or vertical? can you ask employees to post on the topic of your news on their own blogs (assuming it is relevant to do so)?
  • companion posts on external/friendly blogs: do you know of people in the community around your company (you have one, right?) who might be eager to write about your new product or service?
  • posts on media/blog sites, resulting from pre-announcement briefing of appropriate media outlets.

Note that I am advocating for use of a formal news release. Multiple reasons, including the fact that news releases through wire services reach people who might not otherwise see the news – and also appear in news aggregation sites. They also serve as a formal statement of public record for many companies. The act of creating a news release also ideally has the effect of helping you tune your message and get it down to the essentials. (Or not, given some of the lousy news releases I’ve seen come through my inbox.)

Keep in mind, too, that my list is just a guideline. Maybe you want to include an audio podcast – or a slide presentation posted to your SlideShare account – or a supporting white paper. Whatever works for you… the point is that you are just creating multiple pieces surrounding and complementing your news release.

THE RATIONALE OF MULTIPLE COMPONENTS

Beyond the obvious effect of having multiple pieces go out at the same time and create the wave of headlines, there are some other reasons for creating the package:

  • Reaching different subscriber bases – Some people will want to read your news in Twitter. Some will in RSS. Some in email. Some in dedicated sites like YouTube. Some will be interested in a particular aspect of how your news applies. In some cases you might be able to distribute pointers to your news release in all those channels. In some cases you may want to create channel-specific content.
  • Addressing different learning/consuming styles – Some people want just short, brief summaries. Some people want detailed technical info. Some people will prefer to watch a video or a screencast rather than read an article. You can address these audiences through different pieces. Have the formal news release… then put the concise summary on your corporate blog, or perhaps a “news summary” page. Post a technical deep dive on a developer blog. Put a video up on YouTube. Create a summary post somewhere linking all of this together.
  • Enabling others to tell your story – You want to make it easy for other people to tell your story to their audiences. If it’s a compelling story that people will want to share, make it easy for them to do so. Provide the pictures, the screenshots… make the video embeddable (and please don’t make it “auto-play”!)… make this all easy and “self-service” so that people who want to write about your story can do so.

Creating the “package” of pieces lets you do all of this.

THE MULTIPLE HEADLINE EFFECT

An advantage of building a package like this, too, is that you can also try out different headlines in the different components of the package. The main news release can have the more formal headline:

XXXXX ANNOUNCES REVOLUTIONARY PRODUCT YYYYY

The main corporate blog post can say:

Our Product YYYYY cures cancer, solves world hunger and more

while another post on a targeted blog can say:

How Product YYYYY Delivers 6-Month ROI to the Financial Industry

or:

Man, check out how Product YYYYY smokes the competition

You get the idea… multiple headlines, each of which appears then in those various tools and searches monitored by media/bloggers/others. You have a chance to see what will work.

ASSEMBLING THE PACKAGE

Obviously, putting together all the pieces like this can take a good deal of effort… and time. Generally the process will be something like this:

  1. Finalize the news release in advance of the launch date. Depending upon your capacity to produce online content (i.e. how quickly you can do so), you’ll need that news release some amount of time in advance… 24 hours? 48 hours? 72 hours? More? You need the news release signed off on for your final messaging – and also to get to those who will prepare companion pieces.
  2. Determine the URL of the news release. If you can know the URL where your news release will be when it goes live, you can pass this along to those writing companion pieces so that they will link back to the release on your site.
  3. Determine the launch time and date. (And remember timezones when relaying the info) This is important for communicating to those who will write supporting pieces. Ideally you would like the various pieces to hit in the same general timeframe. This is also incredibly important with regard to who will see your stories. If you are in the US, do you want to go live in the early morning US Eastern time? (probably) Or for a European audience?
  4. Develop your companion pieces. Some of the companion pieces can be developed in advance and tweaked with final messaging – others may need final messaging before you start them. (For instance, video may involve too much post-production to re-do, and so you may want to wait for final messaging.)
  5. Deliver pre-announcement briefings. To anyone writing companion pieces, internally or externally, as well as to media sites interested in writing about your news.

And so on… most of this at this point is “PR 101” in how you gear up for an announcement.

UNLEASHING THE WAVE

At the designated time and date, ideally your news release goes out over the wire… your own blog posts appear… your video is live on YouTube… and the stories start appearing.

Some of this you can prepare in advance. Most blogging platforms let you schedule posts. Videos can be uploaded to YouTube and set to be private (which then also gives you the URL you can add into the wire service when setting your news release to go). Other content can be ready in offline editors for posting. Regardless, there will be work to do to make it all start flowing.

Once it starts, you need to make sure you have a tweet (or several) going out in Twitter, a message going out on your Facebook fan page, in Friendfeed and any other services you use.

After that, it’s engaging in the conversation in the real-time media, responding to comments, retweeting other stories you see appearing, and all the other things we do these days.

MEASURING THE WAVE

It should go without saying that if you are going to put this much work into preparing for a release, you need to understand in advance how you are going to measure the results. What kind of web analytics do you have available to you? Can you include custom (and therefore trackable) URLs in your pieces? Can you use URL shorteners like bit.ly that can track usage?

At a higher level… do you have an idea of what constitutes success?

Entire blogs and blog posts are written on the subject of measurement – be sure you have a plan.

PREPARING FOR PROBLEMS

What happens if someone runs with the story before you are ready? What happens if your video doesn’t work? Or your web site goes down? Or one of the companion web sites? All the usual concerns you need to think about…

IN THE END

If you do this right… with a compelling story… an solid “package” of complementary materials… good headlines, etc., the opportunity is there to see this “attention wave” pass through the real-time aspects of the web today and generate some coverage. If it works well, you may indeed see the wave grow for a while.

There are no guarantees, of course. You may do all of this and at the time you go live there is some major disaster… or some celebrity action… (or Apple product release)… or something to divert attention away from you. But your odds of getting attention are way better than when you were thinking of just issuing that one news release.

THOUGHTS?

This way of thinking about what we are aiming to do as an “attention wave” works for me… but I am curious to hear your thoughts, feedback, criticism and opinions.

What do you think of all this? Do you think this is realistic? Unrealistic? A good way to think about the process? Or just the same basic stuff PR has been aiming for but given a slightly different spin? Any pieces I’m missing above?

Have you used a process similar to this in the past? How did it work for you? What problems did you run into?

Have you seen particular companies, organizations or brands that have stood out in your mind for using a process like this? Anyone specific – or any specific announcement – stand out in your mind? Pointers to examples left in the comments would be greatly appreciated.

Any other comments or feedback?


If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or identi.ca.


OSCON WordPress MU slides online – video coming soon

Last week out at O’Reilly’s OSCON, I gave a talk “Creating a Corporate Blog Portal Using WordPress MU“. As I mentioned on Voxeo’s Behind The Blog, I have now put the slides for the talk online. I did record the talk on video – and aim to get that video up online next week. Meanwhile, here are the slides:


If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or identi.ca.


Technorati Tags:
, , ,

“United Breaks Guitars” took far less than a year to hit 1 million views!

When I initially wrote about the “United Breaks Guitars” video two days ago, it only had about 15,000 views. On his website, Dave Carroll wrote this:

At that moment it occurred to me that I had been fighting a losing battle all this time and that fighting over this at all was a waste of time. The system is designed to frustrate affected customers into giving up their claims and United is very good at it. However I realized then that as a songwriter and traveling musician I wasn’t without options. In my final reply to Ms. Irlweg I told her that I would be writing three songs about United Airlines and my experience in the whole matter. I would then make videos for these songs and offer them for free download online, inviting viewers to vote on their favourite United song. My goal: to get one million hits in one year.

No worries about hitting 1 million in one year… this morning as I write this the count is:

1,351,943

Under four days since it was posted July 6th! (Probably hit a million in 3 days.)

Dave Carroll obviously hit a public nerve, too, as he has now been all over the television world… CNN with Wolf BlitzerCBC… CBS Morning Show… and comments on YouTube have indicated its popping up on TV in all sorts of different parts of the world. Mainstream media has covered him, too… some examples include the Halifax Chronicle Herald, the San Francisco Chronicle, the LA Times.

It has, of course, been all over Twitter (also another search).

His “SonsOfMaxwell” Facebook page and MySpace page chronicle some of all the ensuing craziness.

As he said in his website post, he really does need to thank United. This one little video (and only the first of three planned) has really propelled him to a global stage… no way to really know but you’d have to imagine that SonsOfMaxwell have no doubt sold a good bit of music online in the past few days (you see mention of people buying in various comments). It helps, too, that Carroll seems very honest and transparent about this whole thing and that in this case it does seem like United was clearly in the wrong, even if he didn’t file his claim within the 24 hours United’s policies require.

unitedairlines.jpgTo their credit, it’s good to see that United is responding. Their updates to their unitedairlines Twitter account clearly state that they are sorry, that they are working to make this right by him, and that they will be using this video for internal training purposes. The CNN video also refers to a statement from UAL.

It would be interesting to see what, if anything, United does to work with him on subsequent videos. Video #2 is apparently nearing completion, but it sounds like video #3 is still open… could be an interesting opportunity for them if they were interested. It would be fun if they invited him to sing at some United event. Externally, they seem to be putting a good face on it. Internally, no doubt some folks are cringing.

Also interesting to note that Taylor Guitars has so far been low-key on their Twitter account, not really responding or jumping into the conversations on Twitter. They did, though, post this piece about safe air travel with your guitar on their website that does not refer to Dave Carroll or the ongoing issue directly, but does give tips about how to safely travel with your guitar. That piece is also pointed to from Taylor Guitar’s home page.

All in all another great example of how in the age of social media your customers are in control and, if you don’t provide appropriate service, have multiple avenues to voice their frustrations.


If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or identi.ca.


Technorati Tags:
, , , , ,

I will miss Kodachrome (though I haven’t used it in years…)

kodak.jpgI was sad to learn recently that Kodak has ended the 74-year-run of its Kodachrome film. The Wikipedia page on Kodachrome has some good info and links – and Kodak themselves put onlne a tribute site to KODACHROME.

In my younger years, I was seriously into photography and shot tons of rolls of slide film. When I was the University of New Hampshire in the mid-1980’s, I used to put together slide shows for public events for the NH Outing Club (an outdoor activity group, i.e. hiking, canoeing, skiing, etc.). Admittedly, working on the typical student budget, I shot mostly Ektachrome in those days due to the cheaper cost of processing, but in later years I did use Kodachrome quite a good bit. I used it on various trips out west… on a trip to Greenland… in many different places. There was just something about the colors in the film. Great to shoot with.

The reality, though, is that I haven’t bought a roll of Kodachrome, Ektachrome or really any film in probably…

fifteen years.

Maybe even more. Now, between jobs, family and other activities, my photography activities dropped off and the 35mm cameras and lens all sit in the basement… as do the many, many trays of slides… waiting for the mythical time when I’ll have the cycles to scan them all in to my digital photo library.

I’m obviously not alone in that. Here’s question #1 in Kodak’s FAQ:

Why has Kodak decided to stop offering KODACHROME?
Due to declining customer demand for KODACHROME, continued production of this film in no longer viable. Over the years people have moved from KODACHROME to other methods of capture, be it new films or digital. Simply put, not enough people are shooting KODACHROME for us to continue offering it.

And that’s the thing, isn’t it? We’ve all gone digital with our photography. When was the last time any of you actually bought film?

Let’s be honest, too… how many of us really want to go back to using film? The convenience of digital photography is just far too great to even remotely think about going back. Even now, I’m watching the prices of DSLRs continue to drop and keep waiting to jump back into doing more photography with higher-end gear…

Still, it’s sad to hear of the passing of such a great institution within the world of photography.

I may just have to find a roll of Kodachrome before it all is gone, dust off the camera and lenses and go off for a picture-taking spree… just for old times sake…

R.I.P., Kodachrome…


If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or identi.ca.


Technorati Tags:
, , , ,

Twitter’s SPOF Stupidity Continues: Ever hear of redundancy?

twitterlogo.jpgWhile much of the blogosphere is currently dwelling on how great it is that Twitter is postponing its maintenance to allow Iran-related communication, my mind is still reeling from reading the Twitter blog post, particularly this part (my emphasis added):

A critical network upgrade must be performed to ensure continued operation of Twitter. In coordination with Twitter, our network host had planned this upgrade for tonight.

Like Chaim Haas, my reaction is… why is that “network host” singular?

Given the millions of people now using Twitter on an ongoing basis… given the incredibly large ecosystem of applications and systems linking in to Twitter… given the very real communications uses that Twitter has evolved to have… given all of that:

why does Twitter not have redundant connections?

This is really “Network Infrastructure 101” when you are supplying a hosted service. Anyone providing a cloud-based service should ensure that they have redundant network connections… redundant providers… redundant everything. Coming from a company (Voxeo) that provides a hosted application platform, it boggles my mind that Twitter would need to take its system down for “network maintenance”. We would never do that… our customers wouldn’t stand for it!

And that is perhaps the issue… we have customers… Twitter has users.

We ensure that we have multiple redundant providers and networks… because our customers pay us to ensure that their applications are always available. Twitter can get by on “best effort” – and on a single network provider – because no one pays…

Twitter continues to be a massive…

Single Point Of Failure

One company… providing a messaging infrastructure… obviously based on one network provider.

This is my personal frustration with Twitter. I’ve been using it for now 2.5 years or so and continue to see so many benefits to Twitter, yet as someone who has been involved with computer networks for 25+ years, the very idea of a SPOF is hideous. I’m much more interested in distributed architectures like what we see with Laconi.ca and Identi.ca,(As I wrote about a year ago.) or what Google seems to be promising with Wave.

Yet Twitter’s simplicity… it’s directory of users… it’s easy APIs… it’s ecosystem… all of those things keep us using its services…

So while I commend Twitter on listening to their users and postponing their maintenance window… I ask as a long-time user –

why do they need a maintenance window?


If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter (when the service is up!) or identi.ca.


Technorati Tags:
, , , , ,

Initial thoughts on Nambu as a Mac Twitter client

nambulogo.jpgRecently in a bit of frustration, I decided to shift from using an Adobe AIR-based Twitter client on my Mac over to using Nambu, a native Mac OSX app. My frustration is due to the fact that all of the major AIR clients – Seesmic Desktop, TweetDeck and Twhirl – seem to suffer from the problem of consuming a serious amount of CPU usage on my MacBook Pro. I don’t know if this is an inherent issue of using the AIR abstraction layer, which is another layer sitting on top of the operating system, or if the problem lies more in the programming of the applications themselves.

Whatever the case, in frustration this week when my CPU was yet again high and the Activity Monitor showed that the second highest app was one of the Twitter clients, I went off and installed Nambu to give it a try. (The application which is inevitably sucking up the most CPU on my Mac is Firefox… which is why I’m dearly waiting for the real build of Chrome so that I can find and kill off tabs of poorly-written web pages!)

So far, I’ve been very pleased with how Nambu works. Most importantly for me, I can use multiple Twitter accounts. (I tweet from both @danyork and @voxeo and occasionally a couple of others.) All in all the experience is very similar to that of Seesmic Desktop or TweetDeck. There are, though, some differences which I thought I would note here while I think of them:

  • “Compose” field is at the bottom of the screen, versus the top as in TweetDeck and Seesmic Desktop. (Not bad, just different and takes some getting used to.)
  • “Compose” field doesn’t stay open after you tweet. So if you flip to the Nambu window you can’t just click in and start typing. You have to either click the “Compose” button at the top or press Cmd+N to start a tweet.
  • Both TweetDeck and Seesmic (and other Twitter clients) have this UI component where you can go over the picture of someone and have actions right there to either reply, retweet, direct message, etc. In Nambu you have to either click the gear icon on the opposite end of the tweet and then go down to a menu choice… or click on the tweet and click on one of the buttons on the menu at the top. (For me, one value in a desktop Twitter client is speed and the ability to just quickly scan through and act on various tweets. Single-click action buttons are nice for this.)
  • Inability to resize the columns. Ideally I’d like to see more columns on the single page (so that I can visually monitor a bunch of searches at the same time). I’d like to make the columns smaller if I want. (Note that I can’t really resize the columns on Seesmic or TweetDeck, either.)
  • “Sent” column doesn’t differentiate between tweets/replies and direct messages. All are just shown as “sent”. It would be nice if there was a visual clue as to which ones are direct messages.
  • When you click on someone’s twitter name, such as “@danyork”, you get a list of their recent tweets – but I couldn’t see any way to reply to a tweet from that window. I had to click a button to go to their Twitter page to do that.
  • That I could see, there was no “in reply to” feature that would show that a tweet from someone was in reply to another tweet. Now… Nambu does have a VERY cool feature that replies to a tweet are threaded underneath the main tweet… if you can find that original tweet. If you can’t find that tweet, though, you are left not easily knowing what the original tweet was.

Again, overall I’ve been quite pleased with Nambu in the few days that I’ve started using it… I’ll write more here as I use it more.

Comments are, of course, welcome.


If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or identi.ca.


Technorati Tags:
,

Demo of iMovie ’09 image stabilization (before and after)

Given that I’m using Apple’s iMovie software for my Emerging Tech Talk video podcast, I was intrigued by the idea of the new “image stabilization” feature in iMovie ’09. The concept is simple enough – iMovie simply compares one frame to the next, finds the matching patterns and adjusts the frames so that the patterns line up from one frame to the next. This will either remove or reduce the “shake” that happens when you are recording with a handheld camera.

After recently purchasing Apple’s iLife ’09 (admittedly primarily for the iPhoto improvements), I thought I’d give the iMovie stabilization a test. I chose one of my Emerging Tech Talk videos that I recorded with my little JVC camera down at ITEXPO earlier this year:

I just recorded this with Transnexus CEO Jim Dalton out in the hallway outside the conference rooms. I was holding my JVC camera in my hand and trying to brace it against my body to keep it stable.

I honestly didn’t really realize how much the image was moving around until I watched it carefully afterwards.

Now here is the version after iMovie ’09 image stablization:

What do you think? I thought the stabilization turned out rather well.

From a workflow point-of-view, performing the image stabilization was just another step in the iMovie ’09 post-production process. I selected the video clip (the entire segment is one “clip” in iMovie), clicked on the “gear” icon, chose “Clip Adjustments”, clicked the checkbox next to “Smooth clip motion”, pressed “Done”… and waited. It did take several minutes on my MacBook Pro… I’m not sure exactly how long, but it was a number of minutes.

I’ve not yet imported any video from my camera since moving to iMovie ’09, but it appears that there is a checkbox during the import that you could check so that movies go through the stabilization process during import. Obviously this will lengthen the import process, but would then get you on your way to editing with a smoothed out image.

I’ll have to try it out on some other clips, but so far it looks like it could be a useful tool for working with movie clips shot with a handheld camera.


If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or identi.ca.


Technorati Tags:
, , , , , , ,