Andrew Dodson

@ratheeshkannan what can you do with OAuth2 that you can't do with the current OAuth1 version? - since both have their drawbacks right now.

@isaac2004 i've marked this as Good First Issue, hoping someone will investigate the latest Yahoo API and rework the Hello Yahoo module accordingly.

Google API since writing the initial module in Hello.JS began supporting POST'ing activities, see HTTP spec https://developers.google.com/+/domains/api/activities/insert Also the google module shouldn't fail like this. I will try and spec...

I think this has to do with the POST requests needing the token to be sent via the Authorisation header. Its a piece of work which is waiting for someone...

no news

Damn https://blogs.dropbox.com/developers/2016/06/api-v1-deprecated/

Works for me

Hmmm, so this comes from https://github.com/MrSwitch/hello.js/blob/v1.15.1/src/hello.js#L1332 Can you share the value of p.state before decodeURIComponent and JSON.parse - which throws the exception. Thanks

So the `p.state` value looks to be truncated by the Identity Provider > state: "{"client_id":"5604af1c-1e07-481d-8b13-785ea44014c5","network":"hbp","display":"page","callback":"_hellojs_51us82fq","state":"","redirect_uri":"http://localhost:4200/camera?morphology_folder=L2dwZnMvYmJwLmNzY3MuY2gvcHJvamVjdC9wcmbG9naWVzLzIwMTcuMDEuMDU%3D" It starts with a `{` and should end with a `}`. Perhaps the character `%3D`...

That's a good question. Yes as you've pointed out the refresh_token might be a bad idea should there be a risk of script injection etc in your web app. However...