Google — Clueless or Misleading?

Disconnect was covered by the Wall Street Journal (blog) today (note to future Disconnect scribes: this underline thing is called a hyperlink). The post features the work of one of Google’s master bunko artists, whom I’d like to debunk for you:

Google spokesman Chris Gaither declined to comment on Disconnect, but said that users can also turn off search personalization by removing their Web history. (Instructions are here.)

The change Google suggests is strictly cosmetic — their search results will be displayed differently (i.e., not personalized), but your queries and cookies will still be logged by them and kept for 18 months.

Disconnect: Month One

On Disconnect’s one-month birthday, I thought I’d share some usage bits and bobs. Here’s a performance snapshot from Monday — Disconnect is now the 112th most popular and 67th highest rated of the 11,000-odd extensions and themes in the Chrome extension gallery and Facebook Disconnect, the 84th most popular and 10th highest rated (the user and install data is anonymous and collected by the extension system not the extensions themselves):

More importantly, commenter Chris dug up this mind-blowing video about Facebook Disconnect (the Facebook Blocker extension noted in the video hides rather than blocks Facebook resources so isn’t a suitable privacy-protecting substitute for Facebook Disconnect on Firefox or Safari):

100,000 Disconnect’ers

Sometime today, Disconnect and Facebook Disconnect combined got their 100,000th active user on Chrome. Disconnect was released exactly one week ago and had 25,170 users as of yesterday. Facebook Disconnect was released exactly two months ago and had 74,417 users.

That the extensions, with no viral features, marketing, or PR (I just gave TechCrunch an exclusive preview of Disconnect), are now being run by 100,000 people each week is a clear message to Facebook, Google, and every other Internet company that they can’t take our data without our permission anymore.

Meet Disconnect

My 2,686th, and Last, Day at Google

I left Google a month back (and have been doing a little hacking since). I’m told posting your farewell email is all the rage, so here goes:

From: Brian Kennish <bkennish@google.com>
Date: Fri, Nov 12, 2010 at 12:15 PM
Subject: My 2,686th, and Last, Day at Google


(Some of those were Saturdays, Sundays, and days I was pretending to be sick.)

Seven years, six jobs, four teams, three offices, and two coasts later, I’m turning in my Google badge. I’ve been getting asked for three-and-a-half years, “Why are you still here?” The answer was simple: devrel.

I’m certain the developer-relations job and team are the best things about Google. I can finally admit: I can’t believe you can get paid to help startups and independent developers build cool stuff — I’d do so for free. The people on this team and those we work closely with are amazingly talented and dedicated and I’m feeling lucky I got to learn from many of you. Most of all, I want to thank Mike for turning this ragtag bunch of misfits into an important and respected part of Google. We’ve come a long way and I don’t know another manager who would’ve gotten us so far.

I wish I could say goodbye to everyone and have hardly had a chance to to anyone. But if I linger, I might end up changing my mind. Please stay in touch. You can get a hold of me by replying-all to this message (my personal address is in the “To:” field). And I’m pretty easy to find on the web now — a year and a half of developer advocacy and I’ve totally pwned the other three Brian Kennishes in Google search results.

Boo! Facebook Disconnect’s Scary Install Dialog

It’s Halloween, a good time to answer a frequently asked question about this scary confirmation box that pops up when you install Facebook Disconnect:

Google Chrome Extensions, like all installable software, can potentially do bad things and the extension gallery displays accordingly dire warning messages. Unlike compiled programs, though, extensions let you easily view their (HTML, CSS, and JavaScript) source code to make sure they don’t actually do anything malicious.

Facebook Disconnect triggers a warning because the extension has to inject JavaScript into every page you browse to disable the component Facebook links. There are three ways to get a packaged extension’s code (a topic worthy of its own post), but you can just look in my repository since I’ve open-sourced Facebook Disconnect.

Update (December 3, 2010): If you’d rather take my word for it than read my code — Facebook Disconnect doesn’t store your personal data and never will, unless you opt in to anonymously provide data for diagnostic purposes in the future.

Facebook Disconnect Logo

I’ll have more to say about the making of and response to the Facebook Disconnect extension later. For now, I’m dumping all different sizes of the logo I made for you to post. These images are licensed under the Creative Commons Attribution 3.0 License (the same license Creative Commons marks their own work with).

Spread the word!

140 x 140:

128 x 128:

64 x 64:

48 x 48:

32 x 32:

16 x 16: