Galaxy Watch 5 Review Specialty Foods Online 'She-Hulk' Review Disney Streaming Price Hike Raspberry Girl Scout Cookie $60 Off Lenovo Chromebook 3 Fantasy Movies on HBO Max Frontier Internet Review
Want CNET to notify you of price drops and the latest stories?
No, thank you

Jonathan Schwartz's Twitter Q&A posted

After a technical oversight prevented the head of O'Reilly Media from asking Twittered questions of Sun's CEO at a keynote address, both of them go beyond the call of duty to follow up.

O'Reilly Media's Tim O'Reilly posted a blog Saturday with a set of answers from Sun CEO Jonathan Schwartz to questions posed via Twitter by audience members at the Web 2.0 Expo keynote address on Friday morn. O'Reilly Media

Better late than never, as the saying goes.

On Saturday, O'Reilly Media's Tim O'Reilly put up a blog entry with a series of answers from Sun Microsystems CEO Jonathan Schwartz that were in response to Twittered questions from the audience at their Friday morning keynote address at the Web 2.0 Expo.

The post was a result of O'Reilly's having offered the audience at the keynote address the ability to ask questions of Schwartz via Twitter, but subsequently not posing any of those questions.

Afterward, O'Reilly offered a mea culpa on CNET and via his Twitter account, saying that he had inadvertently had his mobile phone set up to receive only Twitter posts from people he follows. That meant that he didn't see any of the audience's questions on his phone.

This is a nice resolution to the situation. In his blog post, he presented Schwartz with 11 questions that had come from Twitter, along with the Sun CEO's responses.

And in fact, this turned out to be a better outcome than if O'Reilly had taken a Twitter question or two because there were only a few minutes left in the keynote when he made the offer. This way, anyone interested in what Schwartz had to say got a much deeper set of responses from him.

So, kudos to O'Reilly for following up and to Schwartz for taking the extra time to respond to the questions. This all turned out to be a good example, after all, of incorporating the backchannel into conference proceedings and showed that everyone involved had the class and courtesy to take the situation seriously instead of just blowing it off to bad luck.