4 ms·
I've heard from people at Google that the reason they don't want to open up posting over the API is because they don't want people's streams filled with robot c
by mmastrac 15y ago
I've heard from people at Google that the reason they don't want to open up posting over the API is because they don't want people's streams filled with robot cross-posts from Twitter, Facebook and zillions of other services. I happen to agree with this point of view.
- danmaz74 15y agoBut what is worse: A stream full of reposts, or an empty stream? It's each user's resonsibility to choose what to post (or repost) or not... Google could just give lower priority in the "filter" to reposted content.
- jamesgeck0 15y agoGoogle Buzz had a lot of import sources available at launch. There was so much noise from automated cross posting that I didn't even know that several of my friends were actively using the service until months later. In contrast, Google+ is almost completely signal for me right now.
- wyclif 15y agoYes, I was waiting for someone to bring up Buzz. I was also a first-day user of Buzz, and guess what? They allowed third-party import, and very quickly out-of-context Twitter updates overwhelmed my stream. Then there was a backlash, and the smarter people turned them off rather quickly. But the vast majority of people kept on using it. I think Google knows exactly what they are doing here.
- nooneelse 15y agoNot all the G+ streams are empty, so that dilemma only really has one horn. Bot-posting would raise the noise floor so as to swamp the current (small) signal. Better to attempt growing the signal itself before adding in a bunch of noise that the users will have to sort through. Now, if one could separate off each user from their bots... that would be neat. Maybe default to only circling a user, but show that they have some bots which one can also subscribe to, if one wants.
- Apreche 15y agoI have a page for my podcast. I want my podcast's web-site to automatically post about new episodes to G+ the same way it does for Twitter and Facebook. If people don't want it, they can just unsub.
- barredo 15y agoMaybe they should allow api-posting to pages, and not to users.
- mindcrime 15y agoSounds like throwing the baby out with the bathwater to me. I have a hard time seeing how one can justify avoiding providing something that users of a service are desperately eager for, and which would undoubtedly help grow the ecosystem around said service, all because of one potential negative consequence. And especially one that, at the end of the day, people can simulate anyway by just posting the same content (by hand) to G+, Facebook, Twitter, etc.
- backspace 15y agoKey words: "by hand" -- posting spam by hand doesn't scale. That's what it's preventing.
- jamesbritt 15y agoI have a hard time seeing how one can justify avoiding providing something that users of a service are desperately eager for, ... How do people know what g+ users are "desperately eager for"? Have there been studies? Polls?
- tobyjsullivan 15y agoI'll bet Google's done the studies and polls. And I'll bet they are seriously considering the response: "We don't want API-driven auto-junk filling our streams!"
- mindcrime 15y ago"We don't want API-driven auto-junk filling our streams!" Nobody does, but - again - we're talking about throwing the baby out with the bathwater here. Not everything posted via API is "junk."
- jamesbritt 15y agoNot everything posted via API is "junk." True, but enough of it is to make it a problem. What could Google do to trap the noise but allow the signal? Rate limiting? Pattern matching against Twitter posts?
- passionfruit 15y agoThis is exactly what happened to Google Buzz.
- hugorodgerbrown 15y agoThey have already allowed certain product vendors access to the write API - more details here - http://adwords.blogspot.co.uk/2011/11/third-party-tools-to-help-manage-your.html http://adwords.blogspot.co.uk/2011/11/third-party-tools-to-h...