I’m not interested in screwing over developers. When we open an API, we want developers to feel confident that the innovations they build are going to be long lasting. Releasing an API, and then later changing the rules of the game isn’t fun for anyone, especially developers who’ve spent their life’s energies building on the platform.
As much as I want a full read/write Google+ API, I still believe Google’s approach has been the right one. They learned from Buzz. The History API shows they can solve some of the most common problems in new ways. It’s nice to see a social network communicate clearly with developers and properly manage expectations.