Paul Bryant has a blog post entitled How Microsoft could crush Google in one easy step. Seriously. where he writes

Henry Blodget has a post up on "One way for Microsoft to Kill Google" It's interesting, but I think there's a much easier and faster method that Microsoft could use to more effectively “kill” Google tomorrow if they so chose.

It’s more than a little bit evil - - but on the other hand, I never heard Microsoft promise that they wouldn’t be:

So what is it?

The height of simplicity. Introduce an integrated ad-blocker to Windows (purely as a customer service, of course) that blocks all Google ads in both IE and Firefox.

Allow users to temporarily or permanently turn off the blocker if they choose. (Knowing full well that 95% of users use just the default settings.)

MSFT would probably need to block their own ads too, in order to make the effort legitimate, but how big a loss would that be for them really, on a relative basis?

For G, on the other hand, it would literally eliminate their entire revenue stream. Overnight. And Microsoft could push this out via a Windows Update in a few weeks time, at most. Buy the very excellent AdMuncher and bundle it if it’s too time consuming to build.

Part of me hesitates to point this out (in fact, I first thought of it a couple of years ago, and didn’t say anything for that very reason) but I can’t possibly be the only person who has thought of this, right? What am I missing?

Usually when I see a post like this, I just post a comment pointing all the ways the idea is stupid problematic. However given that the Paul Bryant's blog doesn't allow comments and I'm supposed to be on vacation, I'll just let the merits of this idea stand on their own without further comment.

I just arrived at London Heathrow and can look forward to another 9 hours or so until my flight to Nigeria. In the meantime, I've found complimentary Web access in the business class lounge so it looks like I won't be bored. I am a little worried about keyloggers and spyware on this computer given how easy it was for me to install Firefox on it. Here are a couple of quick thoughts I had on the way related to links I've seen over the past 24 hours

• Shelley Powers has blog post on newly announced vulnerabilities in popular AJAX libraries. It seems this is another cross site request forgery (XSRF) issue similar to the one found in GMail a few months ago. I remember blogging about mitigations to this issue in my post The GMail Security Flaw and Canary Values when the flaw was announced. I suspect that XSRF will be the new 'buffer overflow' and 'SQL injection attack' of the Web, I expect we'll see a lot more of these kinds of attacks over the next few years before the technology and technologists will catch up with basic safety practices.

• Thomas Hawk and Mike Arrington are continuing with their attempts to stir up an online lynch mob to hang Amazon for shutting a site that was screenscraping and hotlinking to their content. Arrington's post is entitled Amazon’s War on Statsaholic while Hawk's is So it Looks Like Amazon.com Is Going to Be a Jackass and Sue Statsaholic. Nothing beats the blogosphere when it comes to misplaced righteous indignation. A couple of my readers pointed out that the issue is that Amazon initially supported the service then changed their mind. Ignoring the fact that in this 'Stay the Course' world there is nothing wrong with changing your mind, let's look at the facts.

  1. Some geek builds a snazzy AJAX UI on top of screenscraped Alexa data named Alexaholic and sends announcements to Web 2.0 gatekeepers who give it a thumbs up.
  2. Developer on Amazon's blog gives a hat tip to Alexaholic.
  3. Amazon business folks get involved and realize some guy is building a competitor to their service with their own proprietary data and server resources then shut him down.

  As a geek, I think Alexaholic is cool. as someone who actually works on large scale Web services and knows that these services cost millions of dollars to build and maintain, I know why the last thing you want is some competing service built on screenscraping your data then showing its own ads on top of it. Heck, even Google has realized that APIs that allow competitors to build competing services on your data + resources while circumventing your ads are a bad idea so why is it wrong for Amazon to do the same thing?

  This reminds me of Don MacAskill's post on Enterprise Linux where he points out that he saves money on enterprise Linux for his business by buying rebranded/repackaged versions of RedHat Linux from RedHat's competitors like Oracle's Unbreakable Linux and  CentOS because they undercut Red Hat on price on their own software. Is that really the world Arrington and Hawk want to force "Web 2.0" companies into? Well, screw that. More power to Amazon.

  PS: Amazon is probably wise to let it go against Alexaholic mainly because it hurts the messaging around their Web Platform story. Morally they are in the right but bad press never cares who's right, does it?

• Thanks for all the book suggestions. I ended up going with Ender's Game and Freakonomics from the suggestions. I also got three Discworld books, Anansi Boys and Dune. I'm halfway through the Neil Gaiman book and although it isn't as good as American Gods it is still an enjoyable read albeit a little slow to start off which I guess was on purpose.
  

• It looks like there is a new version of Live Maps according to the team blog. This product has now officially gone through more names than I've had ex-girlfriends. It's been named MSN Virtual Earth, Windows Live Local, Windows Live Maps, Live Search Maps and now Live Maps. It's sad that we are intent on screwing one of the coolest products we are shipping these days in this way. :(

  Anyway, check it out at http://maps.live.com

• This is another summer that promises a bunch of movies from cartoons and comics that rocked my childhood. Fantastic Four: Rise of the Sliver Surfer, Spider-Man 3 and Transformers all look hot. The trailer for Transformers was initially disappointing because it looked like there were too many humans and not enough robots but the newly released pics from the movie make it look like my fears were unfounded. Sweet.

• I saw Forest Whitaker the last time I travelled to Nigeria in the Virgin Atlantic upper class lounge. I wonder if I'll meet any celebrities this time around? I doubt it though given that British Airways is a step down from travelling on Virgin Atlantic. Damn that Richard Branson.

Mike Arrington has a blog post on TechCrunch entitled Amazon’s War on Statsaholic where he writes

Statsaholic (formerly Alexaholic) launched a year ago and provided much easier access to Alexa traffic data than the Alexa site itself. Statsaholic also had other features Alexa didn’t offer, like embeddable graphs and data smoothing. Others agreed, and soon started linking to Statsaholic instead of Alexa when doing traffic comparisons. At one point, Alexa was the no. 3 search result on Google for “Alexa.”

Statsaholic was not using the Alexa web service to get the data, because Alexa doesn’t offer the graph data via their web service. Amazon, which owns Alexa, could have complained or simply shut them down when it launched, but they didn’t. They actually complimented the service in a post on the Alexa blog last April.
...
What bothers me about the situation is that Amazon sat on it for a year, complimenting the service along the way (and copying it). Then, just when the service started getting really popular, they took drastic measures to shut it down.

I'm totally perplexed by Arrington's position here. Statsaholic is screenscraping Alexa and building a business on top of that. It seems like a pretty open and shut issue to me. The fact that Amazon didn't bother prosecuting them until they got a lot of traffic just points out that there is little point harassing folks who are abusing your service unless they are consuming a lot of your resources or are taking money out of your pocket. It seems Statsaholic was doing both. 

You'd think a smart startup founder would know better than to build a business model on hotlinking and bandwidth theft. You'd also expect a Web savvy dude like Mike Arrington to know better than blame the victim in such situations. Next thing you know, he'll be flaming websites that block hotlinking to their images via htaccess. Weird. 

PS: Someone in the comments wondered how Mike Arrington would feel if someone created a mashup that showed all of the TechCrunch content minus the obnoxious ads (e.g. http://techcrunchminusads.com). I wonder if Mike would sue if the site started stealing a bunch of his traffic  since it wouldn't load so many ads thus being faster and perhaps included more useful info (e.g. crosslinking TechCrunch posts with PodTech interviews)? 

The Yahoo! Developer blog has an entry entitled Introducing the Yahoo! Mail Web Service which states

While we are certainly proud of the success of Yahoo! Mail, today we are announcing how we are going beyond the boundaries of the Yahoo! network and enabling developers to build new tools or applications around Yahoo! Mail. We are thrilled to announce the open availability of the Yahoo! Mail Web Service, web service for Yahoo! Mail (accessible via SOAP or JSON-RPC) that we previewed to Yahoo! Hack Day attendees. With the Yahoo! Mail Web Service, you can connect to the core mail platform to perform typical mailbox tasks for premium users such as list messages and folders, and compose and send messages (you can also build mail preview tools for free users with limited Web Service functionality). In other words, developers outside of Yahoo! can now build mail tools or applications on the same infrastructure we use to build the highly-scaled Yahoo! Mail service that serves nearly 250 million Yahoo! Mail users today -- users who might want to help you make some cash with your application.
...
The Yahoo! Mail Web Service is a big release for Yahoo! and the Internet, and it's only the beginning of what you'll be seeing from Yahoo!. Jump into our code samples for Java, .NET, PHP, Perl and Python, and build your dream mail app today, then be sure to give us feedback on your experience so we can continue to make the API even better. Be sure to leverage the online Yahoo! Mail Web Service support group where you can get help from the Yahoo! Mail Web Service team and your fellow developers. We can't wait to see what applications you will build when you add your imagination to the platform. Maybe you want to build an application that backs up Yahoo! mail targeted at a large number of Yahoo! users, or maybe you just want to add a niche feature that makes Yahoo! Mail better for your mom. For inspiration, we've gathered a few applications:

• Yahoo! Mail Search (Mail Plus)
• Flickr Postcard
• Yahoo! Mail with Flickr Image Association

First things first, this is an unprecedented and very welcome move on the part of Yahoo! This is another example of why I think of the three major Web portals, Yahoo! has done the best job of turning their services into a developer platform. I like the fact that the Web service is exposed over multiple protocols and the code samples are in multiple programming languages that run the gamut from enterprise developer fare (Java/.NET) to Web geek fare (Perl/Python/PHP). Mad props to the developer platform folks at Yahoo!, good work.

With that out of the way, there is some stuff that has me scratching my head after taking a look at the Yahoo! Mail Web Service User Guide and API Reference. The first thing that is weird is that although Yahoo! provides SOAP and RESTful JSON web services for accessing one's mail, I still can't get POP access to my Yahoo! mail without shelling out $20/year. After all, GMail has POP access for free and users of the free versions of Windows Live Hotmail can get POP-like access if they use Windows Live Mail desktop although they are restricted to using one mail client.

So I decided to see if the Yahoo! Mail Web Services provides a way around this restriction but found out from the section on "Determining the Users Account Capabilities" that

The Yahoo! Mail Web Service limits the functionality available to free accounts. Premium accounts have no such limits. First call the GetUserData method to get the user’s account type from the web service.

Account Types

●	Premium Users

Premium users may access any part of the web service. There are no restrictions.

●	Non-Premium Users

Non-Premium users are restricted to the following APIs:

ListFolders	ListMessages	DeleteMessages
GetUserData	BatchExecute	CreateFolder
FetchExternalMail	RemoveFolder	RenameFolder
MoveMessages	EmptyFolder

Calls to other APIs will return an error.

So it looks like I actually can't build an application that can be used to read the actual mail messages from my Yahoo! Mail account with the API unless I'm a premium user. Otherwise, all I can do is list the messages but not actually get their content. That makes the APIs a lot less cool than I initially thought. 

Like Sam Ruby and Paul Downey I initially wondered about the choice of exposing a SOAP API but then realized that it may be that they already use SOAP internally so this wasn't that much work for them in that case. I also wondered about the lack of a RESTful non-SOAP XML interface as well but after looking at the complex object models I can see why they went with data formats that are pretty much serialized object models (i.e. Javascript OBJECT Notation & Simple OBJECT Access Protocol) instead of expecting developers to write a bunch of gnarly XML parsing code for processing over a dozen different response formats from the 23 methods in the Yahoo! Mail Web Service.

I suspect that Yahoo! won't get as much traction as they expect with the API until they remove some of the restrictions on non-premium accounts. Even then it does look like there is enough to build Windows and Windows Live gadgets for Yahoo! Mail that show your messages. Except that there is no way to read the mail contents and not even a way to link to the message in way that sends the user to Yahoo! Mail to read its contents. I bet if Yahoo! fixed the latter and perhaps had a rev-share with people who drove clicks back to the Web-based mail client, things would get very interesting. I wonder if Jeremy is listening?

Dave Winer has a post entitled How basic is Twitter? where he writes

So inevitably, a query about the value of namespaces leads you to wonder if there will be TwitterClones, web-based services that emulate the Twitter API, that keep internal data structures similar to Twitter, and most important, peer with Twitter, the same way Twitter peers with IM and SMS systems.

This is as far as I got in my thinking when last night I decided to ask Les Orchard, a developer I know for quite a few years, and who I've worked with on a couple of projects, both of which use the kind of technology that would be required for such a project --

What if there were an open source implementation of Twitter?

Nik Cubrilovic happened to be online at the moment and he jumped in with an idea. Les confessed that he was thinking of doing such a project. I thought to myself that there must be a lot of developers thinking about this right about now. We agreed it was an interesting question, and I said I'd write it up on Scripting News, which is what I'm doing right now.

What do you think? Is Twitter important, like web servers, or blogging software, so important that we should have an open source implementation of something that works like Twitter and can connect up to Twitter? Where are the tough sub-projects, and how much does it depend on the willingness of the developers of Twitter #1 to support systems that connect to theirs?

The problem I see here is that Twitter isn't like web servers or a blogging engine because Twitter is social software. Specifically, the value of Twitter to its users is less about its functionality and more about the fact that their friends use it. This is the same as it is for other kinds of social/communications software like Facebook or Windows Live Messenger. Features are what gets the initial users in the door but it's the social network that keeps them there. This is a classic example of how social software is the new vendor lock-in.

So what does this have to do with Open Source? Lots. One of the primary benefits to customers of using Open Source software is that it denies vendor lock-in because the source code is available and freely redistributable. This is a strong benefit when the source code is physically distributed to the user either as desktop software or as server software that the user installs. In both these cases, any shabby behavior on the part of the vendor can lead to a code fork or at the very least users can take matters into their own hands and improve the software to their liking.   

Things are different on the "Web 2.0" world of social software for two reasons. The obvious one being that the software isn't physically distributed to the users but the less obvious reason is that social software depends on network effects. The more users you have, the more valuable the site is to each user. Having access to Slashcode didn't cause the social lock-in that Slashdot had on geek news sites to end. That site was only overtaken when a new service that harnessed network effects better than they did showed up on the scene (i.e. Digg). Similarly, how much value do you think there is to be had from a snapshot of the source code for eBay or Facebook being made available? This is one area where Open Source offers no solution to the problem of vendor lock-in. In addition, the fact that we are increasingly moving to a Web-based world means that Open Source will be less and less effective as a mechanism for preventing vendor-lockin in the software industry. This is why Open Source is dead, as it will cease to be relevant in a world where most consumers of software actually use services as opposed to installing and maintaining software that is "distributed" to them.  

Granted, I have no idea why Dave Winer would like to build an Open Source competitor to Twitter. The main thing that will come out of it is that it will make it easier for people to build Twitter knock offs. However given how easy it is to roll your own knock off of popular "Web 2.0" social sites (e.g. 23, SuperGu, Uncut, etc) this doesn't seem like a lofty goal in itself. I'm curious as to where Dave is going with this since he often has good insights that aren't obvious at first blush.

This post was originally meant to be a response to Mini-Microsoft's blog post entitled Mini, a Devil, and Fine Whine where he seems to imply that there is some sort of class struggle going on at Microsoft and also made some calls for radical transparency. However this morning Mini linked to a blog post entitled For want of a shoe, or time for a new rider? on the MSFTextrememakeover blog which is just fire and has distracted me. If you're a Microsoft watcher [or even better a Microsoft exec] you should go ahead and read it, twice even. Key excerpts that lit my fire

Mission

MSFT does not appear to have a clear, honestly customer-focused mission that is understood at all levels. Importantly - and perhaps as a result - employees seemingly aren't in total accord or fully bought into it. If MSFT truly believes in "Your potential. Our passion", then it needs to do more than just pay lip-service to it. It needs to open itself to all that that entails (cross-platform support, not playing lock-in games, etc.) and deliver against it.
...
Culture

I see two concerns here. First, the need to move from a culture of "good enough" to one of "excellence" and "insanely great". I've posted about this before. MSFT has a long-standing approach, ingrained via Gates, of getting something - anything - out to market and then fixing it over time. That worked well for a long time when "free" alternatives weren't prevalent, and when competitors/markets weren't moving as quickly as they are today. Now, it's a lot less successful, and yet MSFT continues to do it and be surprised when it fails.
...
Prioritize/Focus

Stop fighting major wars on multiple fronts simultaneously. It is simply ridiculous for current management to assume that MSFT can fight the biggest and best companies on earth, across a dozen or more battlegrounds, and still hope to prevail. Just take a look at some of the folks MSFT is going up against: SONY (and Nintendo) in gaming, Nokia and many others in mobile, GOOG and YHOO in Search, Everyone from Alcatel to Siemens in IPTV, IBM/Oracle/SAP (and smaller players Salesforce.com. Rightnow, etc.) in ERP and CRM, IBM/Adobe/FOSS in middleware and development, AAPL and most of MSFT's former partners in mobile media, AAPL and GNU/Linux in Operating Systems, and FOSS in personal productivity. Worse, these battles are spreading MSFT too thin, and leaving its core cash cows increasingly vulnerable (would Vista have taken 5 years to develop if management hadn't been distracted with a dozen other battles?).
...
Public Face

I am sick and tired of MSFT executives "trash" talking competitors in public. This is such a fundamental business tenet that it's an embarrassment to have to even list it.

Like I said, the entire post is really good. As for my response to Mini's Mini, a Devil, and Fine Whine post, here it goes. The kind of people who focus on what the top X% of Microsoft are making are probably not the kind of employees you want to keep around anyway so it seems weird to be catering to them. The concerns that the Microsoft employees whose opinions I value have are all eloquently described in MSFTextrememakeover's post excerpted above. The kind of people who get in a tizzy because some VPs got to attend an expensive award ceremony that they didn't are the kind of whiners and losers you can never make happy so why bother? It's not like they can argue that they are underpaid or that their employment benefits suck. Instead I see it as part of the age of entitlement in America where lots of people believe they deserve to be balling out of control and then gets pissed off when they aren't. The best thing you can do with those kind of people is to show them the door. 

I'm traveling to Nigeria next week to belatedly celebrate my dad's seventieth birthday and I'm looking for suggestions on what I should read on the trip. It usually takes about 24 hours of traveling for me to get back home; 8 hours flying to London, 10 hour lay over and another 6 hours to Abuja. I usually go through 2 or 3 of Terry Pratchett's Discworld books on my trip but that often isn't enough. The last time I was back home, I also read Malcolm Gladwell's The Tipping Point and the time before that I read Neil Gaiman's American Gods. Both books were interesting and I'm considering reading their sequels (i.e. Blink and Anansi Boys) on this trip.

However I recently stumbled on a list of the 50 most significant Science Fiction and Fantasy works of the last fifty years and I'm considering getting one or two books from that list. Oh yeah, and then there's Jeff Atwood's recommended reading list of books about software development which has a few entries that caught my eye as well.

Given that you now know my taste in in-flight reading material, what books would you recommend gentle reader?

Back in the day, before Microsoft realized the power of bloggers to create positive buzz about a product I often had to chime in on discussions about why it was important to take into consideration the opinions of the vocal minority in the blogosphere. One of the things folks like Robert Scoble and myself would point out is that mainstream reporters often get their stories from blogs these days. This means that if a product is getting a lot of good press among a few key blogs it eventually makes it into the mainstream media.

The best example of this I've seen in recent memory is the hype storm around Twitter. The tipping point in mainstream coverage of the service seems to have been when a bunch of bloggers who attended the SXSW conference started using the service. According to Google Trends interest has been increasing steadily in the service but mainstream coverage was lacking until after SXSW. Since then we've had articles like 

Business Week: Twitter: All Trivia, All The Time
Wall Street Journal: Friends Swap Twitters, and Frustration
San Francisco Chronicle: Austin's SXSW festival atwitter over Twitter

With results like this, it is no wonder PR flacks of all sorts are circling blogs and other antisocial media like groupies at a rock concert hoping to infect us with their disease message.

Raymond Chen has a blog post entitled You don't know what you do until you know what you don't do where he writes

I've seen a lot of software projects, and one thing I've learned is that you don't have a product until you start saying "No".

In the early phases of product design, you're all giddy with excitement. This new product will be so awesome. It will slice bread. It will solve world hunger. It's designed for everybody, from the technology-averse grandmother who wants to see picture of her grandkids to the IT manager who is in charge of 10,000 computers. It'll run equally well on a handheld device as in a data center.

When I see a product with an all-encompassing description like this, I say to myself, "They have no idea what their product is." You don't know what you do until you know what you don't do. And the sooner you figure out what you don't do the better, because a product that promises to do everything will never ship.

In my five years at Microsoft, I've seen a bunch of projects fail. Some were public flame outs that are still embarrassing to mention today while others are private mistakes that you'll never hear anyone outside the b0rg cube mention. A few months ago I wrote a blog post entitled Top 5 Signs Your Project is Doomed and since then I've considered a few more entries that should be on the list bringing the total to 10. The list below are common signs that a  software project is doomed. Meeting one or two of these criteria isn't necessarily the kiss of death but three or more and you might as well start circulating your resume. 

1. Trying to do too much in the first version. See Raymond's point above.
   

2. Taking a major dependency on unproven technology.
   

3. Competing with an existing internal project that was either a cash cow or had backers that are highly placed in the corporate hierarchy.
   

4. The team is understaffed. If you have less people than can handle the amount of work you have to do then the right thing to do is to scale back the project. Practically every other choice leads to failure.
   

5. Complexity is one of the goals of the project because "complex problems require complex solutions".
   

6. Schedule Chicken
   

7. Scope Creep

8. Second System Syndrome

9. No Entrance Strategy. When a project can't articulate how it goes from a demo or prototype to being in the hands of end users, there's a problem. This is particularly relevant in the "Web 2,0" world where many startups only strategy for success is getting a mention on TechCrunch and the fact that their service has "viral" features.

10. Tackling a problem you don't know how to solve. It's pretty amazing how often I've seen this occur.
    

According to the Infoworld article entitled Microsoft names leaders for search-and-ad unit

Microsoft Wednesday named Satya Nadella to lead the newly formed Search and Ad Platform group, the software giant's effort to optimize the advertising revenue-raising potential of its search business.

Nadella, previously corporate vice president for Microsoft's Business Solutions group, will report to Kevin Johnson, president of the Platform and Services Division, the company said in a statement.

I'm not sure this information is accurate since I haven't seen any sign of it on Microsoft Presspass nor has Satya Nadella's corporate profile been updated. However if it is, it would then create three VPs under Kevin Johnson who are in charge of Microsoft's three Web brands; Windows Live, MSN, and Live Search. The org chart representing all the folks who are in charge of Microsoft's online businesses would then be 

if the Infoworld article is accurate.

The only relevance this has to people who read my blog is that it gives a nice visual of where I fit in the org chart. I'm in Blake Irving's group, working on aspects of the Windows Live Platform that powers services used by the Windows Live Experience group.