<story><title>Sign in with Google has been removed for your privacy</title><url>https://slimvoice.co/login</url></story><parent_chain><item><author>sys42590</author><text>Why do they argue with privacy?&lt;p&gt;If Google decides to lock your account for any reason, all your third party accounts using Google&amp;#x27;s SSO are mostly fubar, as it&amp;#x27;s currently almost impossible to get your Google account back.</text></item></parent_chain><comment><author>jchw</author><text>If you use SSO with the account you &lt;i&gt;were&lt;/i&gt; going to use your e-mail address with, it makes little difference whether you used OAuth2 vs traditional e-mail based authentication. You&amp;#x27;re locked out.&lt;p&gt;If something happens, like OAuth2 stops working, most websites allow password reset to the e-mail address connected to the account, and then can log-in without OAuth2.&lt;p&gt;The concern here is &lt;i&gt;probably&lt;/i&gt; related to some Log-in with Google scripts that run on the frontend, although if they were just using normal OAuth2, then I think they are wasting their time: whatever sensitive information Google gets via OAuth2 they also get via the unencrypted e-mails you&amp;#x27;re sending to them anyways...</text></comment>
<story><title>Sign in with Google has been removed for your privacy</title><url>https://slimvoice.co/login</url></story><parent_chain><item><author>sys42590</author><text>Why do they argue with privacy?&lt;p&gt;If Google decides to lock your account for any reason, all your third party accounts using Google&amp;#x27;s SSO are mostly fubar, as it&amp;#x27;s currently almost impossible to get your Google account back.</text></item></parent_chain><comment><author>bloomingeek</author><text>F-ing Google locked me out of my account and my email because I broke my cell, and then traded it in for a new one but Google kept sending the verification to my broken cell. There&amp;#x27;s no one to call for assistance!</text></comment>