Two cowboys ride off into the sunset. The younger of the two was brought in to do a specific job for a limited time, while the older has been around for what seems like forever.

I refer respectively to Google Gears and Microsoft Internet Explorer 6. We’ll start with the latter, the browser that would not die, but that seems to have got a lot closer to extinction this year.

The IE6 story is well told, mainly in comic strip form, by Brad Colbow at Smashing Magazine. (By the way, I like Smashing enough to suggest that you sign up for its newsletter and for a chance to win some of the cool giveaways.)

So, on to the story of the Mountain View Kid: Google Gears. Gears’ most striking feature is that it allows you to access the web without an internet connection. It is of course necessary that the browser and the sites you’re using are Gears-enabled.

So why can the Kid? Because offline access to the web belongs in web standards. So Google has shifted effort away from Gears itself and “towards bringing all of the Gears capabilities into web standards like HTML5″ (quoting from the Gears API blog).

Reaction to the Gears news seems to have been positive. To some, it looks good because standards are good (and I think they are usually better than the alternative). To others, the news about Gears looks good because Gears itself wasn’t (and my own limited use of Gears did yield some rather weird results).

MG at TechCrunch thinks that Gears deserves to die because it is guilty of being a plugin, and plugins fragment the web. While I see what he means, I don’t think all plugins are equally guilty. For example, without Gears, I need an internet connection to access the web, but I’m used to that. Flash is far more guilty: without it, much of the web is unusable.

In sum, I’m glad that each of these two cowboys is taking a last ride. To mix metaphors, the web will be a less tangled place without them.

Thanks to German Vidal for making the photo available under Creative Commons.

50 millions tweets a day? It has indeed come to this, as Mashable Ben and many other sources report. The statistic reminds me, as I’m sure it reminds many others, of the Bruce Springsteen song “57 Channels (And Nothin’ On).”

But of course, there are things on, on TV, and even on Twitter. It’s just that I can get the content I value through other channels.

When it comes to social media, I can subscribe to your blog. When it comes to TV or movies, I can catch you on Netflix, or… Perhaps I’m stuck in the middle, liking old-school social media such as blogs and feeds, and new media channels for movies and TV, such as Youtube and Netflix.

I am impressed with 50 million tweets as quantity. I’m still waiting to be impressed by Twitter when it comes to quality.

R is for Recommendation. So TrustR is a metric for Trust and Recommendation: it’s used in a study just published by Millward Brown. On a scale where the average brand scores 100, and anything over 105 is considered good, Amazon wins with 123, with FedEx just one point behind.

Then there are four firms on 120. I’m not sure that there is any statistical significance between them. The last of them, and hence the brand in 6th place, is Tylenol. Toyota is one point behind.

The Tylenol/Toyota juxtaposition is particularly interesting in the light of the recent Toyota Trust(R) turmoil. I’ve posted about it before, prompted in part by a post in which Gene of Levick made the Toyota/Tylenol comparison.

I found out about the study via Om: a blogger/person/source/brand I’m inclined to trust and recommend. I’m also inclined to trust and recommend Amazon.

Did the Lorax Drive a Prius?

February 19, 2010

I just read The Lorax to my son. Many of Dr. Seuss’ books remain fresh, but this one seems particularly relevant at the moment. Here’s a quote. (Which character? See last paragraph for the answer.)

I meant no harm. I most truly did not.
But I had to grow bigger. So bigger I got.
I biggered my factory. I biggered my roads.
I biggered my wagons. I biggered the loads.

The growth imperative features, not only in this 1971 book, but also in a 2010 story: Toyota sacrificed quality for global growth and got burned (as the Washington Post puts it). That’s particularly sad since Toyota is so strongly identified with the quality movement. If Toyota did indeed sacrifice quality for quantity, then it betrayed the very principle that made it one of the world’s great organizations.

For more on the current Toyota story, see… all over the web, but particularly my previous post and a professional PR perspective.

But back to the Lorax we started with: here’s his statue, in a sculpture garden I wish I’d visited when I lived nearer to it.

The Dr. Seuss National Memorial Sculpture Garden is now open at the Springfield Museums in Springfield, Massachusetts, the city where Theodor Seuss Geisel was born and which appears to have inspired much of his work.

The Lorax is the shortish, oldish, brownish, mossy, and bossy environmentalist in the story that bears his name. The Once-ler is the industrialist quoted above.

This blog, like millions of others, is hosted at WordPress.com. I’ve been very happy with the service.

I’m still happy with it, despite today’s downtime. I have to applaud Matt’s downtime summary. He didn’t attempt to downplay the downtime. He quantified it, to the tune of 5.5 million lost pageviews (not all of which are mine, I must admit).

I had to smile when I first saw the news about the downtime. It was a Mashable post about “tweets pouring in.” That just reinforced to me how much more robust WordPress.com is than Twitter, which I still think functions best as the home for the fail whale.

Good post title, huh? I didn’t make it up. I copied it. It’s fine for me to copy it, as long as I give proper attribution. Even if there were no such thing as fair use, it would still be fine for me to copy “Music Journalism is the New Piracy.”

That’s because the Electronic Frontier Foundation and Tim Jones, who posted under the same title at the EFF’s blog, placed that content under the Creative Commons Attribution License. That’s the same license I use for this blog, by the way. Tim’s post is about the recent deletion of six music blogs at Blogger, which is owned by Google.

Although the takedowns were made in the name of stopping piracy, the deleted blogs do not appear to have been hotbeds of illegal file-sharing… In at least one case… accusations of copyright infringement were almost certainly incorrect.

Tim’s post links to a list of web hosts that cherish free speech. I wasn’t previously aware of the list, or of any of the hosts on it, so I thought it worth remarking on.

TechCrunch has a thing,or a place, called the Deadpool. It’s where social media companies go when they shut down. A look at TechCrunch posts tagged deadpool shows two arrivals so far this year: EventVue, and Yahoo’s Shopping API.

I’d say that these two closings are rather different things. Although each sees the end of a web service, only one sees the end of a company. EventVue is no more, while Yahoo lives on to… well, probably to close more services, among other things.

Yahoo shutting down an API is more like an amputation than a death. Amputations may be gruesome, but the patient is still alive, and may be in better health after the operation.

I want to focus on a couple of recent amputations, each at and by a different widget company. One of the companies is Sprout, which I seem to be moved to cover around this time every year. Two years ago, widgets were hot, and Sprout particularly hot and fresh, drawing quotes such as “SproutBuilder is going to explode the world of widgets on the web.”

Sprout Builder was launched as a freemium service. A year later, in January 2009, the free part (almost) went away. Now the Sprout Builder subscription service is now more. This was pointed out in a comment on this blog by Sumit Chachra (who I find to be the CTO of Tivix, a social media platform for nonprofits).

Sprout Builder is an example of the Amputation Ward, rather than to the Deadpool, because Sprout the Company still exists. What is Sprout now? Its home page answers that question as follows. “Sprout technology allows brands to engage their audiences across the social graph.” I won’t dig into what that actually means – at least not right now.

The current post is more about the amputation of Sprout Builder. Sprout’s blog post, which was published yesterday (i.e. on a US holiday), refers to a “service transition.”

One of the toughest decisions that a start-up faces is where to focus its efforts and resources. Sprout Builder was our first product and has always been near and dear to our hearts. More importantly, we value the customers who have gotten us to where we are today. However, we have made the hard decision to shut down the Sprout Builder subscription service to focus on our enterprise product lines. The only service level that we will continue to offer for Sprout Builder is geared towards enterprise customers. The cost is $2999 a year.

There hasn’t been a lot of coverage of the amputation yet. But a post by Heather Gardner-Madras has already drawn a few comments, all to say the least disappointed with the impending disappearance of sprouts by subscription.

Clearspring is the other service-amputating widget company. Clearspring blogged the news under the title: AddThis, our universal sharing platform. The first half of the post is indeed about AddThis, which Clearspring acquired in 2008. Then:

As AddThis now supports widget sharing, today we’re also announcing our plans to deprecate our original Clearspring Launchpad platform in April of 2010. After that point, the original Launchpad widget-sharing platform will no longer be available and AddThis will be our one sharing platform. Widgets will continue to run until the beginning of 2011. All the while, we will continue to improve the ability of AddThis to share embeddable content…

For long-time Launchpad users, we realize that there are some steps required to transition… We’ve put together comprehensive documentation to help you move from Launchpad to AddThis. We’ve also setup an area on our forum.

Some of the reaction to the deprecation/amputation is on the forum. I won’t link there, since it requires login. A post at Widgetmatic states that those using the Launchpad platform have some transition work, or some broken web pages, ahead of them.

Let’s take a look at some of the differences and similarities between these two amputations. The obvious similarity is that each involves a company that used to be in the widget business, and now downplays the term widget. Sprout seems to have purged the very term from its system. Clearspring is amputating its “widget platform” to focus on its “sharing platform.” I’d say that the idea of a widget, in the sense of a chunk of code that can be embedded on web sites, is alive and well, but that the term has fallen from favor.

The main difference between the amputations relates to market segments. Sprout is cutting off its smaller customers, in order to concentrate on enterprise clients. Clearspring seems to want to keep its customers, and to transition them to its favored platform.

Some Clearspring users will indeed transition to AddThis. Some will transition to a platform offered by a different provider, perhaps reasoning that Clearspring has pulled one platform from under them and might pull another. Yet other Clearspring users will simply let their widgets die on deprecation day.

I come into the last of these groups. I got very excited when I found that it was possible to use Clearspring widgets at WordPress.com, an environment hostile to many widgets. I’m inclined to be relieved that my excitement died down, and that I didn’t get heavily into developing Clearspring widgets for others to use at WordPress.com.

So that was a first visit to the web’s amputation ward. I hope that it wasn’t too gruesome. I also hope that it illustrates the difference between the amputation ward and the deadpool.

WordPress and Google Buzz

February 15, 2010

Google Buzz is a platlication: it’s both an application and a platform on which applications can be built. It’s been a busy application, seeing millions of people and posts in its first couple of days.

It’s also been a busy platform. I have a particular interest in the applications that bridge Buzz and WordPress. So does Mashable, as we can see from today’s post. It’s mainly a roundup of the plugins that put Google Buzz buttons on self-hosted WordPress blogs. As such, it doesn’t live up to its title: HOW TO: Integrate Google Buzz Into Your WordPress Blog.

I’m interested in an aspect of blog/buzz integration that the Mashable post doesn’t cover: having my WordPress posts show up in Google Buzz. There is a way to do this that works both with blogs hosted at WordPress.com (as this one currently is) and with WordPress blogs hosted elsewhere (such as Andrew’s Wanderings).

In short: you tell Google Webmaster Tools that you own the blog in question; then Google Buzz will allow you to add the blog to your list of connected sites. I found out about this at the WordPress.com forums, which in turn linked to an amusingly untitled blog for details.

By the way, there does seem to be a way of putting a Google Buzz button in a post at WordPress.com, but I haven’t tried it.

French Bread FaceSo I just buzzed my first buzz. I’m not kidding about the bread-making, and I’m certainly not kidding about the blizzard.

I was going to add belated to the post title. I kept on checking my Gmail, since I knew that to be the notification mechanism. But there was no email about it, so when I checked Gmail via my iGoogle home page, I seemed Buzzless. Then I went to Gmail itself, and saw the invite there, albeit not in a mail.

In my crusty mood, I thought I saw a grumpy face on one of the baguettes I made. It is my new Google profile image, and hence my Buzz icon.

Blizzard But No Buzz

February 10, 2010

Recent snowstorms have prompted my daughter (6) to ask if we are in a blizzard. It certainly looks like one outside.

This snow day might be a good opportunity to try out Google Buzz. But I am so far buzzless…

Follow

Get every new post delivered to your Inbox.

Join 77 other followers