Google shows a scary message that discourages people from using it

[clonm]

Is there a cooperative way we can get Google verification so that this message doesn't pop up when people click "sign in to Google"? House president is saying account creation is a barrier to people using PeerMind at Cloyne.

[mitar]

Interesting. Thanks for reporting this. It seems I have not seen it because you do not get this warning for your own app. Anyway, it seems the issue is because I am requesting permissions to access your Google Plus contacts (so that the app could suggest you people to delegate to). It seems this is seen as sensitive by Google (which, based on latest Facebook fiasco is probably reasonable), so I would have to go through verification process. For that, I think we would first have to:

• Migrate all instance to one domain (peermind.org),
• Have a privacy policy.

More info:

• https://developers.google.com/apps-script/guides/client-verification

So for now I cannot do much about this.

[clonm]

Suggesting people to delegate access to seems like not core functionality. What would it look like to just remove the Google+ contacts permission, would it be easy to get verified then?

[clonm]

I see this should theoretically be fixed by 3fe9088, but the same error still displays on cloyne.org - has the version on cloyne.org been updated?

Related: running it locally is crashing for me right now but peermind/account/services.coffee shows

  # If user is not already signed in, then we do not allow them to sign in
  # but require them to first sign in with username and password.
  throw new Meteor.Error 'unauthorized', "You can sign in using #{_.capitalize serviceName} only after you linked that account to your existing PeerMind account." unless userId

The main benefit of being able to log in with other services, is to reduce the cognitive overhead of creating a new account/password. If an account has already been created for an email address, why not let them log in with the social account immediately without having to create a password?

[clonm]

Confirmed: After clicking through the scary warning and granting permissions, trying to log in with google as [email protected] still shows an error, even though that account has a username/password set up: