Google+ sign in helpful tips

While implementing the G+ sign in on my site, there were a few "need to know" things that were buried in the documentation.

Hopefully this helps someone.

I'm using the HTTP API.

The "old" system uses the scopes:
https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email

whereas the new one uses:
https://www.googleapis.com/auth/plus.login https://www.googleapis.com/auth/plus.me<

Update: Actually you still need to use
https://www.googleapis.com/auth/userinfo.email

auth/plus.me does return a bunch of useful profile information, though.

You'll see the auth/plus.login fairly quickly while reading the API docs, but mention of the auth/plus.me is a little buried.

In the docs the person GET request looks like
GET https://www.googleapis.com/plus/v1/people/userId

 

If you're just using auth/plus.login scope, you'll have to request the userid and then make a separate API call to get the person's info. (

OR you use auth/plus.me scope and set "me" as the userid in the GET request.

 

I'll update this as I experiment with the API some more.

 

If you'd like to add anything, leave a comment.

 

related links:

https://developers.google.com/+/api/latest/people/get#examples
http://googleplusplatform.blogspot.com/2013/02/google-plus-sign-in.html

Google+ sign in helpful tips

While implementing the G+ signin on my site, there were a few need to know things that were buried in the documentation.

Hopefully this helps someone.

I'm using the HTTP API.

The "old" system uses the scopes:
https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email

whereas the new one uses:
https://www.googleapis.com/auth/plus.login https://www.googleapis.com/auth/plus.me

You'll see the auth/plus.login fairly quickly while reading the API docs, but mention of the auth/plus.me is a little buried.

In the docs the person GET request looks like
GET https://www.googleapis.com/plus/v1/people/userId

If you're just using auth/plus.login scope, you'll have to request the userid and then make a separate API call to get the person's info. (

OR you use auth/plus.me scope and set "me" as the userid in the GET request.

I'll update this as I experiment with the API some more.

If you'd like to add anything, leave a comment.

related links:

https://developers.google.com/+/api/latest/people/get#examples

Shortcut key to reopen closed tabs in Chrome

Ctrl+shift+T
"Reopens the last tab you've closed. Google Chrome remembers the last 10 tabs you've closed." --chrome keyboard shortcuts


Since I found that shortcut, I notice that I use it quite often.

I saw a funny post (on Google+ I think) that said something like:

"Try browsing with only 6 tabs open at all times"

We all know that never happens.

I've got 7 open right now (not counting multiple browsers.. lol)

 

Unlike Firefox, Chrome doesn't have a "recently closed tabs" history menu.

firefox-recently-closed-tabs

When you accidentally close a tab, getting back to it in Chrome can be a hassle.

So use the shortcut Ctrl+Shift+T and pop it back up! It works on multiple levels (if you've closed more than one tab, it will pop them back up in order).

Chrome's history is annoying to navigate in general. At least they moved the history to the parent directory of options instead of where it used to be in Tools > History.

You can use the shortcut Ctrl+H to get to the history faster, but that still doesn't help the fact that the history is listed chronologically. What if the tab was opened 100 history states ago?

The search feature works pretty well, but if you're like me, you'll forget what the page title was. Thereby rendering search useless.

 

Hope this helps!

If you know a secret shortcut key combo (or a lesser-known one) that you use all the time and want to share it, leave a comment.

Shortcut key to reopen closed tabs in Chrome

Ctrl+shift+T
"Reopens the last tab you've closed. Google Chrome remembers the last 10 tabs you've closed." --chrome keyboard shortcuts


Since I found that shortcut, I notice that I use it quite often.

I saw a funny post (on Google+ I think) that said something like:

"Try browsing with only 6 tabs open at all times"

We all know that never happens.

I've got 7 open right now (not counting multiple browsers.. lol)

 

Unlike Firefox, Chrome doesn't have a "recently closed tabs" history menu.

firefox-recently-closed-tabs

When you accidentally close a tab, getting back to it in Chrome can be a hassle.

So use the shortcut Ctrl+Shift+T and pop it back up! It works on multiple levels (if you've closed more than one tab, it will pop them back up in order).

Chrome's history is annoying to navigate in general. At least they moved the history to the parent directory of options instead of where it used to be in Tools > History.

You can use the shortcut Ctrl+H to get to the history faster, but that still doesn't help the fact that the history is listed chronologically. What if the tab was opened 100 history states ago?

The search feature works pretty well, but if you're like me, you'll forget what the page title was. Thereby rendering search useless.

 

Hope this helps!

If you know a secret shortcut key combo (or a lesser-known one) that you use all the time and want to share it, leave a comment.

Google+ sign in helpful tips

While implementing the G+ sign in on my site, there were a few "need to know" things that were buried in the documentation.

Hopefully this helps someone.

I'm using the HTTP API.

The "old" system uses the scopes:
https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email

whereas the new one uses:
https://www.googleapis.com/auth/plus.login https://www.googleapis.com/auth/plus.me

 

You'll see the auth/plus.login fairly quickly while reading the API docs, but mention of the auth/plus.me is a little buried.

In the docs the person GET request looks like
GET https://www.googleapis.com/plus/v1/people/userId

 

If you're just using auth/plus.login scope, you'll have to request the userid and then make a separate API call to get the person's info. (

OR you use auth/plus.me scope and set "me" as the userid in the GET request.

 

I'll update this as I experiment with the API some more.

 

If you'd like to add anything, leave a comment.

 

related links:

https://developers.google.com/+/api/latest/people/get#examples

Google+ sign in helpful tips

While implementing the G+ sign in on my site, there were a few "need to know" things that were buried in the documentation.

Hopefully this helps someone.

I'm using the HTTP API.

The "old" system uses the scopes:
https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email

whereas the new one uses:
https://www.googleapis.com/auth/plus.login https://www.googleapis.com/auth/plus.me

Update: Actually you still need to use
https://www.googleapis.com/auth/userinfo.email

auth/plus.me does return a bunch of useful profile information, though.

You'll see the auth/plus.login fairly quickly while reading the API docs, but mention of the auth/plus.me is a little buried.

In the docs the person GET request looks like
GET https://www.googleapis.com/plus/v1/people/userId

 

If you're just using auth/plus.login scope, you'll have to request the userid and then make a separate API call to get the person's info. (

OR you use auth/plus.me scope and set "me" as the userid in the GET request.

 

I'll update this as I experiment with the API some more.

 

If you'd like to add anything, leave a comment.

 

related links:

https://developers.google.com/+/api/latest/people/get#examples