Order In the Plex Now

Archive for June, 2011

The Epic Story Behind Google’s Social Plans

Tuesday, June 28th, 2011

No, not here.

It’s here.

Close readers of IN THE PLEX could intuit that I had access to the team behind Emerald Sea, the codename for Google’s social product. It wasn’t done when the book was, so I couldn’t share the details. The essential components are out today, so I was finally able to tell the story behind what is now called Google+.

In one sense, following up on this to deliver the long story I dropped today was a great way to gently decompress after my immersion into Google for the book. I still had a reason to go on campus and talk to a team of Googlers and see what they were up to.

So will it succeed? Depends on a lot. But from the start I was surprised at the degree of urgency in this project. There was a lot of twists and turns before today and undoubtedly there will be more. And I’ll keep watching.

Who Do You Trust? Who Do You Anti-Trust?

Friday, June 24th, 2011

I’ll weigh in later on with some views on the FTC’s now-confirmed probe of Google. For now, let me flick at just one data point. The author of Google’s blog item that acknowledged that it had received government subpoenas–and launched a general defense of Google practices–was not a lawyer. It was an engineer. Specifically, Amit Singhal, a world-class computer scientist who has been sort of the search quality guru at the company for a number of years. He is also utterly captivating when he describes the intricacies of Google’s algorithmic quest for relevant results. This may indicate the tenor of its eventual defense– Google is putting forward its face as data-driven, scientific, and non-judgmental in its treatment of search results.

Much more to come….

How Decisions Made by Twitter Founders in 2006 Led to Anthony Weiner’s Dickish Demise

Monday, June 13th, 2011

Now that the Anthony Weiner Twitter Meltdown has pretty much played out, I’m surprised that there hasn’t been much discussion of the butterfly wingflap that brought him down: Twitter’s rules of engagement when it comes to “following.”

The success of a social network is largely determined by its settings. In 2006, an engineer named Jack Dorsey had an idea for a way for people to share short updates on their lives with friends and family. Working with a small team, Dorsey and his colleagues began developing and testing the product. This included determining the built-in boundaries of the service, a process which would determine the breadth and purpose of the entire project. Twitter was a simple idea but settings had to be just right, like the proper temperature for a soufflé. Should the rules be very restrictive, to preserve privacy and intimacy? (Too restrictive would make the service less useful.) Or should they be expansive, and invite a wide circle to share one’s status reports? (Too broad a channel would mean a depersonalized cohort.)

The breakthrough that enabled Twitter to become the wildly successful service it is now, came from a twist that was much more significant than even its founders knew: they made it possible to “follow” someone’s messages without requiring permission. Essentially you would take out a subscription to someone’s Twitter stream. You would follow your best friend or your brother in the same way you would follow Barack Obama, DeSean Jackson, or the New York Times. This was a break from the traditional two-way agreement that ruled communications in previous social systems. This changed Twitter from an asynchronous instant messaging system into a hybrid of a social network and broadcast medium.

“The relationship model was something that we debated a lot,” says Evan Williams, who headed the company (Odeo) that created Twitter. “In the first version, by default you were private.” (This quote is from a conversation I had with Williams in 2009, when I was working on a story for Wired.) But then Dorsey’s team came up with the idea that you could follow someone without them following you. “That was really important,” says Williams. “From my perspective, I wanted something like a blog relationship model. What I thought was beautiful about blogs as opposed to email or anything else is it’s completely up to the recipient of the information whether or not they consume it.”

But Twitter was much more intimate than blogs. Following someone on Twitter was not exactly like setting up a blog feed or subscribing to a magazine. You became part of a visible community. In order to make this happen, Twitter made public the list of people you followed, as well as the list of people who followed you. You would notice when your friends followed the same people you did. You could make connections with other people who followed the same Tweeters you followed.

To further encourage the community aspect of Twitter, the founders determined that by default, all messages would be public. Weirdly, one of the questions that came up during this discussion was the question whether people would be creeped out when it came to flirting and other personal issues. “This openness was the result of a lot of thought around the way we had started recognizing that people were communicating online,” says Noah Glass, who was part of the original team. (I interviewed Glass for the aforementioned story.) “We were on MySpace, and I got into a lot of trouble from various girls posting things on that thing out in the open, and I started thinking about openness–we all started thinking about openness. We come from a world where privacy is important. But we realized that not everyone shared this feeling about privacy in that same kind of way. People were having really intimate discussions out for everyone else to read. I realized that that the level of privacy we thought was important, was not necessarily important to a certain group of people for a certain type of communication. And so making any conversation open and followable was something based on those systems that were becoming popular.”

This thinking influenced the settings when Twitter, because of user demand, implemented a “reply” feature. The replies, just like any other tweets, were public.

But what if you wanted to have a truly private conversation, as with SMS or email, with someone on Twitter? This presented a problem to those with a huge following. One way to do this would be to allow users to send a private message to any other user, just as they can with email. But celebrities and others with large followings didn’t want to open a private channel to just anyone. So Twitter decided that for “direct” messages there should be some limits. Direct, private messages could only be sent to someone who followed you. The fact that you followed someone meant that you’d probably be happy to hear from him or her. To have a back-and-forth conversation, then, both parties would have to be following each other.

Otherwise, once you hit a few keystrokes to specify that something is a direct message, sending a private tweet is not all that different from sending a public tweet. The service has never really figured a way to foolproof the process. It is a rare Twitter user—even an experienced one—who has not mistakenly sent something intended as a direct message out into the public Twittersphere. Happens all the time.

These settings helped make Twitter catnip for loquacious politicians like Anthony Weiner, who used it to establish his feisty personality with a nationwide community. But it also proved his undoing when he misused Twitter for sordid sexual contact with women.

Twitter’s regimen of rules tanked Anthony Weiner in several ways. First of all, it provided a public record of the initial contacts that Weiner made with the women. Here was the apparent pattern of Weiner’s inappropriate communications: a woman would tweet an encouraging public messages to the legislator—which would be public, the only way she could communicate to him. (By and large, since the women were political supporters and not thinking of themselves as material for his sexual fantasies, this wasn’t a problem for them.) Then Weiner would respond to them—but his responses were constrained by the knowledge that his replies were public.

Weiner needed a more private channel of communication for flirtations up to and including pictures of his package. Since the women followed him already, he could send them direct messages. But to receive their replies, he had to follow them in return. Only then could he engage in flirting or sexual repartee.

Weiner seemed not to realize the extent to which Twitter’s rules still made him vulnerable. The women were publicly listed among those accounts he followed. Since he only followed around 200 people, these new followers seemed out of place among the politicians, journalists, and celebrities on his list. It was all too easy for a political foe to notice that Weiner was adding young women (and in at least one case, a porn star) to his followers soon after a public exchange.

And that is exactly what happened. A right-wing activist noticed Weiner’s pattern and then harassed the young women the Congressman followed. But even then, Weiner did not curtail his behavior. He simply unfollowed those women and found new ones to flirt with. His Twitter use was a train wreck waiting to happen.

The train wreck occurred when Weiner confronted the confusing rail yard that Twitter’s founders never truly fixed: the inadequately drawn distinction between a public message and a direct one. When Weiner decided to send a young woman a picture of his crotch—wearing grey boxers that barely contained his tumescence—he had already taken the step of following her. But he made a common mistake between a direct private message and a public reply, and sent the picture out to the thousands of people who followed him.

That was so crazily egregious that Weiner’s initial lies that his account had been hacked seemed plausible. But the evidence of his deeper misbehavior was already out in the open: the thumbnails of the young women he followed, publicly available on his Twitter account. Journalists, political rivals, and right-wing muckrakers had no problem finding multiple women who had flirted and even received more graphic photos via “private” Twitter messages. When asked about what happened, the women talked, and Weiner’s original “I was hacked” story fell apart.

Weiner was caught in the social net, undone by a bunch of conversations several years earlier between some San Francisco geeks trying to figure out the settings of a cool new product. The details of Web product design had led to the pants being pulled down on a promising political career.

Jobs to PC: “You’re busted!” And other notes from the OS Wars

Tuesday, June 7th, 2011

Steve Jobs’s return to the stage yesterday at Apple’s World Wide Developer’s Conference focused on software. Hardware provides Apple’s brains and sinew, he told us, while software is its soul. Though there were three chapters to the story he spun, the narrative was coherent. Apple was staking its claim in the great Operating System wars in the second decade of this century. Passing through the flak smoke of competitive visions—from Google and Microsoft, natch—Jobs was like a deft bombardier tweaking the flight path before releasing his payload, the Apple Way of modern computing.

(Excuse the horn-blowing, but this pretty much conforms to the outline of the near feature in my Wired cover story that came on the heels of the original iPad announcement in early 2010. Consider this blog post as an update.)

Chapter one is Lion, the latest version of OS X. The mane point (sorry) of this chapter is that the Macintosh is adopting more traits of its iOS cousins. Lion supports more multi-touch gestures. Lion has the app store built in. And so on.

Chapter two is the iOS 5, the system upgrade for iPad, iPhone and the iPod Touch. The features Apple unveiled yesterday imbue these devices with capabilities previously available only on PC’s. With iOS 5, you can edit photos, create more complex mail documents, etc. This accelerates the trend of amazingly powerful apps (Garage Band being the best example) on the iPad.

So while the Mac is morphing into the iPad, the iPad is stepping up to perform tasks that you once reserved for your Mac or PC.

The most telling feature in this transformation is the revelation (greeted with huge applause from the developers in the crowd) that Apple was untethering the iOS devices from the PC. In my Wired article, I had joked that Apple envisioned the day when the main use for your PC is syncing with your iPad. But now Jobs has topped that. Beginning with iOS 5 users won’t need a PC to set up, synch, or update their iPads or iPhones. Jobs even said that he was “demoting” the PC to “just another device.” Talk about a comedown. It’s like busting Jack Welch to a middle manager!

Chapter three is the new iCloud. In this initial rev, iCloud is focused less on full-scale “cloud computing” (moving the performance of the apps themselves to the Web) than on synching a number of devices with one’s personal corpus of data—which resides in Apple’s data center. Apple, he claimed, would achieve success in this model where others have failed. (The most striking example is Microsoft’s Live Mesh system, which you probably never heard of. In that light, a lot of iCloud’s concepts look straight outta Redmond.) Why will Apple triumph? Because, says Mr. Jobs, “it just works.”

Jobs himself took pains to underline the significance of iCloud in the ascension of the new, pad-and-phone-oriented Post PC paradigm. iCloud, he said, marks the completion of a long quest to liberate the computer from local files and all the desktop mishigas involved. (In case you missed it, In the press release he called this the release’s “paramount feature.”) The iPad does away with folders and file icons, but has not offered an alternative means of organizing documents. With the ability to store documents in then cloud, he crowed, the missing piece of the iPad will finally be filled in. (Of course, until now Jobs had never admitted that the piece had been missing. Classic Steve.)

So where does this leave Apple’s competitors, particularly Google? Google’s cloud embrace is still more radical than Apple’s. As of now, Apple regards the cloud as a hub; Google’s Chrome OS treats the cloud as the computer itself. The Chromebooks coming out later this year basically run a superfast browser, with the assumption that Web-based apps and services will provide all you need. (As I noted in my test of the Chrome OS, Google is designing a platform for a high-speed connected infrastructure that’s not here yet.) By comparison, Apple’s cloud is timid: it’s about storage and synching as opposed to a streaming, real-time, extension to your actual machine. At Apple, the action is not on the Web, but in the apps.

Complicating Google’s plans, though, is the fact that it has a second operating system, its Android mobile system. Android is more like iOS is that it runs client apps—and this approach puts it at odds with its corporate, pure-Web stablemate. At the recent Google i/o conference, the dissonance between the two systems was apparent. Each day of the event featured a keynote devoted to one system followed by a press briefing where each team leader (Android’s Andy Rubin and Chrome’s Sundar Pichai) unconvincingly tried to explain why the systems weren’t competitive. Co-founder Sergey Brin addressed the question by saying that owning two promising OS’s was a problem that most companies would love to face.

And what about Microsoft? Last week at the D9 conference, Windows czar Steven Sinofsky allowed us a glimpse of Windows 8. Just as the Mac OS borrows from the iPhone and iPad, Win 8 adopts the flashy interface of Microsoft’s praiseworthy (but not yet commercially proven) Win 7 phone OS. It looks like a bold break from the past. But Sinofsky also explained that the interface will sit on top of a full version of old-style Windows. (I wonder how long the Windows 8 tablet will take to boot up.) “Post PC” is apparently still a taboo concept at Microsoft.

But whether Microsoft admits it or not, we’ve been Post PC for years now. Our problem has been that these new devices haven’t yet morphed into tools that are every bit as capable as the one they’re replacing. At WWDC, Steve Jobs moved us closer to filling that gap. Considering Apple’s unbelievable momentum, you have to believe that that his users will follow.