I thought that was unnecessary, and frankly unprofessional and disrespectful to a major rival.
Google should instead focus on their own platform. The corporation seems locked in a pathological pattern of habits, from trivial sniping at rivals to grand tax-avoidance.
I was impressed to see that the quick start guide for Google+ Platform integration features .NET among other platforms. This seems a refreshing departure from Google's usual attempts to overlook and even downplay Microsoft and its technologies (in line with Google's shameful "Gang of Four" propaganda model).
Google+ is just Google man...it's not just the social network, you're connecting all of your Google cloud into an app, that's a lot more powerful than a purely social website like Facebook.
Your "Google, don't attack other companies!" post would have been taken more seriously, maybe, if you hadn't just attacked Google yourself, 11 minutes prior to that.
The developers (sorry "engineers") forgot to make the Git repos public -- so they're promoting the quick start guide which links to source code nobody can access. The URLs on Google's documentation all give (404 errors).
The official Google+ profile on Github has a grand total of two members (both Google staff).
Much like Google+ its self, this big announcement is not exactly buzzing with comments, either, despite being heavily promoted by every tech website I know simultaneously.
If Google want people to use this, they need to give us URLs that work.
Hi +Tim Acheson: I'm not aware of any 404s on docs associated with Google+ Sign-In. Can you let me know which URLs you're seeing 404s on, and I'll look into it?
@scott See Cecil's post above, but in fact all Git repo URLs in the official Google+ Platform quick start documentation return 404 -- because the repos either do not exist or more likely are not set to allow public access yet. :)
E.g. https://github.com/googleplus/gplus-quickstart-csharp.git
@scott I can confirm I'm referring to the Git repo URLs provided in the Google Developers documentation, which do not exist.
I do sometimes encounter errors on Google Developers (and other Google documentation sites including AdSense etc), ranging from occasional Internal Server Error messages today to broken external links like these. I always try to report them. Folks at Google must be aware that it's easy to automatically crawl pages for broken links as part of ongoing QA/monitoring.
Other broken link examples I encountered today in case it helps:
On this page: https://developers.google.com/commerce/wallet/digital/articles/usingopenid The "article written by the Open ID team" is a broken link: https://developers.google.com/intl/pl/appengine/articles/openid
I sometimes wonder if humans other than me actually look at these pages, let alone Google's own vast legions of staff checking official pages sometimes.
Other examples just from today's browsing:
On this page, the various external URLs linked to from the Google Developers pages are broken links: https://developers.google.com/commerce/wallet/digital/docs/samples#iap-java
The JWT spec link is outdated here and should be updated: https://developers.google.com/commerce/wallet/digital/docs/libraries
Hire me, Google. I can improve your service. I'm serious. But you won't, and perhaps therein lies the problem... ;)
Thanks - looks like the first broken link is now available at https://developers.google.com/appengine/articles/openid, but I'll report that one and the others.
@Scott Knaster do you know if that will be soon later today or much later today? Should I keep trying or come back tomorrow?
I'm probably teaching grandma to such eggs here, but if Google is makes an announcement like this and briefs multiple tech websites, it's daft to have URLs that don't work.
The initial experience of the community with Google+ Platform has not been good. The most eager developers are following your links and getting 404 errors. Dude! Documentation with crucial URLs giving 404 errors is not what we expect from one of the world's richest corporations. Do you test stuff before you go public? All you needed to do is set access to public on the Git repos.
I never reply to troll comments like Tim, but it's "Suck" eggs, not "Such". You seem pretty committed to criticizing the work of others, and yet I'm not even sure you read your comments before they go, 'public'.
Please get rid of the separate app and integrate it in Settings, where almost all included settings can already be found anyway. The separate app is just annoying and unnecessary (plus it's making a lot of people angry, just read the recent reviews in google play.)
I have been curious about why Google did not do exactly that. They chose the complex way rather than the easy way. Maybe they just wanted a stand-alone product to announce, but they missed the point lol.
BTW, it's ridiculous for Fitbit to use this system when Android does not include Bluetooth LE (so Fitbit devices cannot even synchronise via Android devices). Only some of the Samsung devices have BLE implementation.
Love the crack at Facebook about preventing a spray ofn"frictionless" updates. :)
ReplyDeleteI thought that was unnecessary, and frankly unprofessional and disrespectful to a major rival.
DeleteGoogle should instead focus on their own platform. The corporation seems locked in a pathological pattern of habits, from trivial sniping at rivals to grand tax-avoidance.
I was impressed to see that the quick start guide for Google+ Platform integration features .NET among other platforms. This seems a refreshing departure from Google's usual attempts to overlook and even downplay Microsoft and its technologies (in line with Google's shameful "Gang of Four" propaganda model).
Wow, this story is being heavily promoted today.
ReplyDelete"The transition of Google+ from pure destination to a portable identity" (TechCrunch)
So, just what Facebook, Twitter, etc, are already doing -- along with everyone else Google wants to imitate.
And of course, Google will still count these interaction when contriving their spurious inflated Google+ "active user" stats lol.
"Google hasn't had as much success building a vibrant social network as Facebook" (Mashable)
Understatement of the century.
Google+ is just Google man...it's not just the social network, you're connecting all of your Google cloud into an app, that's a lot more powerful than a purely social website like Facebook.
DeleteYour "Google, don't attack other companies!" post would have been taken more seriously, maybe, if you hadn't just attacked Google yourself, 11 minutes prior to that.
DeleteThe github site has no repositories. Where is the code for the quick starts:
ReplyDeletehttps://developers.google.com/+/quickstart/javascript
+Cecil: Sorry for the delay. The code will be available later today.
DeleteEpic fail lol
DeleteThe developers (sorry "engineers") forgot to make the Git repos public -- so they're promoting the quick start guide which links to source code nobody can access. The URLs on Google's documentation all give (404 errors).
The official Google+ profile on Github has a grand total of two members (both Google staff).
Much like Google+ its self, this big announcement is not exactly buzzing with comments, either, despite being heavily promoted by every tech website I know simultaneously.
If Google want people to use this, they need to give us URLs that work.
Hi +Tim Acheson: I'm not aware of any 404s on docs associated with Google+ Sign-In. Can you let me know which URLs you're seeing 404s on, and I'll look into it?
DeleteThanks.
@scott See Cecil's post above, but in fact all Git repo URLs in the official Google+ Platform quick start documentation return 404 -- because the repos either do not exist or more likely are not set to allow public access yet. :)
DeleteE.g. https://github.com/googleplus/gplus-quickstart-csharp.git
Ah, the github repos we know about and we're working on. I thought you were referring to other URLs, like docs on developers.google.com . Thanks.
Delete@scott I can confirm I'm referring to the Git repo URLs provided in the Google Developers documentation, which do not exist.
DeleteI do sometimes encounter errors on Google Developers (and other Google documentation sites including AdSense etc), ranging from occasional Internal Server Error messages today to broken external links like these. I always try to report them. Folks at Google must be aware that it's easy to automatically crawl pages for broken links as part of ongoing QA/monitoring.
Other broken link examples I encountered today in case it helps:
On this page:
https://developers.google.com/commerce/wallet/digital/articles/usingopenid
The "article written by the Open ID team" is a broken link:
https://developers.google.com/intl/pl/appengine/articles/openid
I sometimes wonder if humans other than me actually look at these pages, let alone Google's own vast legions of staff checking official pages sometimes.
Other examples just from today's browsing:
On this page, the various external URLs linked to from the Google Developers pages are broken links:
https://developers.google.com/commerce/wallet/digital/docs/samples#iap-java
The JWT spec link is outdated here and should be updated:
https://developers.google.com/commerce/wallet/digital/docs/libraries
Hire me, Google. I can improve your service. I'm serious. But you won't, and perhaps therein lies the problem... ;)
Thanks - looks like the first broken link is now available at https://developers.google.com/appengine/articles/openid, but I'll report that one and the others.
DeleteAwesome, and the Github repos are now available:
DeleteE.g. Google+ Platform quickstart for .NET.
@Scott Knaster do you know if that will be soon later today or much later today? Should I keep trying or come back tomorrow?
ReplyDeleteI'm probably teaching grandma to such eggs here, but if Google is makes an announcement like this and briefs multiple tech websites, it's daft to have URLs that don't work.
The initial experience of the community with Google+ Platform has not been good. The most eager developers are following your links and getting 404 errors. Dude! Documentation with crucial URLs giving 404 errors is not what we expect from one of the world's richest corporations. Do you test stuff before you go public? All you needed to do is set access to public on the Git repos.
Lol...
DeleteI never reply to troll comments like Tim, but it's "Suck" eggs, not "Such". You seem pretty committed to criticizing the work of others, and yet I'm not even sure you read your comments before they go, 'public'.
PSA: Idiots and idioms, a dangerous combination.
@jimmy Dude, you pick me up on typos and call me the troll? lol
DeleteA day later and still only 9 comments on this? I expected more buzz after all the hype.
ReplyDeleteThere are 17 comments on this announcement if you count mine. There are 8 comments on the page if you ignore the troll lol.
Google+ #tumbleweeds
Please get rid of the separate app and integrate it in Settings, where almost all included settings can already be found anyway.
ReplyDeleteThe separate app is just annoying and unnecessary (plus it's making a lot of people angry, just read the recent reviews in google play.)
I have been curious about why Google did not do exactly that. They chose the complex way rather than the easy way. Maybe they just wanted a stand-alone product to announce, but they missed the point lol.
DeleteBTW, it's ridiculous for Fitbit to use this system when Android does not include Bluetooth LE (so Fitbit devices cannot even synchronise via Android devices). Only some of the Samsung devices have BLE implementation.
ReplyDelete