and others... One thing we like about the +1 with share flow via JS and the sharebox is that it ensures that there is a human
behind the post. We like when there's a human explicitly and intentionally making a post (to their own stream) because we've found that when they are aware of what and where they're posting then they are far more likely to engage with any audience the posts attracts. Not surprisingly, auto-cross-posting has much lower engagement levels, which has a negative impact overall on the ecosystem. It's not just about getting more content (of which there is plenty) but it's also about the quality of the experience when people spend time on Google+. As +Will Norris
says, we're not ruling it out, and we have ideas in mind on how to keep the quality bar high along with offering write access. But at the same time, we're not going to do something foolish for the product (or more importantly, the product's users) just because it's technically
possible to build an API for it. +Matt Mullenweg
The problem with fire-and-forget "publicize" is that the world doesn't need to yet another broadcast / write-only medium. There are plenty of those. (To be clear, I'm not dismissing them, they offer value. But that's not Google+.) Besides, if we're wrong, we can always move carefully in that direction. Turning around and going the other way is much harder.
That said, Salmon is still very
interesting in this context. Even without full bi-directional sync (which again to be clear, I'm not ruling out, especially for comments), having better mechanisms to embed Google+ threads closer to the relevant content could offer value for authors and readers alike. I want
authors to publish on blogs. I love the decentralized web.
Good discussion. I think what +Will Norris
is doing here is both clever and useful. The JS sharebox technique means that his original content is still self-hosted on his own blog, but he is adding a personalized message for his Google+ audience (including the opportunity to explicitly pick the circles) and it all points back to his own domain. Let's keep working on ways to reduce the friction while maintaining the level of quality of Will's approach.