Re:IFTTT.com forced to pull Twitter triggers
by benaiah on Thursday September 20, 2012 @07:01PM
(#4551207)
Except Google+'s non-writeability is more a symptom of Google's crappy API support than anything else. They built a product, and didn't really put any time in to make it a service or a platform.
I think it's apathy rather than malice on Google+'s part.
Re:IFTTT.com forced to pull Twitter triggers
by ihsw on Thursday September 20, 2012 @10:37PM
(#4551927)
Indeed, Google Maps is just about the only polished public API they have. It's really unfortunate that Google is so unfriendly to developers regarding their products.
Re:IFTTT.com forced to pull Twitter triggers
by Spoom on Friday September 21, 2012 @01:47PM
(#4554803)
Google derives their primary revenue from advertising. APIs allow developers to sidestep advertising in displaying Google's content. Ergo, it is not in Google's best interest to allow easy free access to their content, via an API or otherwise, in a place where they cannot control how the content is displayed.
I don't completely agree with this reasoning but I can see why they don't just throw build APIs everywhere.
Re:IFTTT.com forced to pull Twitter triggers
by seltzered_ on Saturday September 22, 2012 @08:16AM
(#4557705)
yep. And honestly, I've been okay with google's model so far, at least until their websites and apps become littered with ads like facebook.
Aside from companies (and sociopath friends) using hootsuite, I've never really heard of anyone using a third-party facebook website or app to post.
google+: a network that restricts that people _write_ via their website/apps.
twitter: a network that is now starting to restrict people to _read_ only via their website/apps.
technology does evolve and diverge in lots of directions.