You'd think that Google would get better at dealing with this situation after, oh, say, <i>six years</i> of having the problems of forced multi-service integration (and abuse countermeasures) pointed out to them:<p><a href="https://news.ycombinator.com/item?id=6746731" rel="nofollow">https://news.ycombinator.com/item?id=6746731</a> [1]<p>But no.<p>Just from my own experience, I've been locked out of my Google account[2], my <i>real</i> Google account[3], and of course, when the company, as it on very rare an infrequent occasions does, cancels services, found myself (and a few million others) scrambling to salvage content and communities.[4]<p>Others have had slightly worse authentication/access situations.[5]<p>To be fair: the problem is a complicated one, and Google sees a lot of abuse. Or, as in Mariplier's community's experience: activity which looks a lot like spam, at a multi-billion-user scale, which can make assessment difficult.<p>(Though as has been pointed out: if scale of operations makes reasonable levels of service provisioning prohibitive, perhaps you shouldn't be operating at that scale?)<p>Google <i>do</i> manage to cull a lot of spam, abuse, and other crud. In my some-time career of trying to get hard numbers regarding aspects of Google+ membership and activity, I found:<p>- G+ communities were being created <i>and deleted</i> at a prodigious clip of thousands per day. Even in the final months of the site, several hundred thousand new communities were added.<p>- A strong predictor for whether or not a G+ profile would be deleted was <i>if it had ever posted public content</i>. By a factor of about 10 over profiles with no visible content. Presumably, many of these were spam or other abusive profiles.<p>- The very most active profiles across a small sampling of recent Communities posts were spammers, and by the time I'd gone back to verify the top few, most or all their content was removed.<p>When you're operating at large scale, it's difficult to make discerning, accurate, fair, or consistent decisions. That's understandable.<p>But <i>you should be aware of this</i> and design systems to recover gracefully from errors. Which includes not discomfitting, annoying, or distressing users excessively. Someting Google have repeatedly failed at.<p>________________________________<p>Notes:<p>1. The day that item ran, the top three items on HN were either directly or indirectly about my experience or frustrations with the then-new Google+ - YouTube accounts merger. <a href="https://i.imgur.com/YgEjUuI_d.jpg?maxwidth=640&shape=thumb&fidelity=medium" rel="nofollow">https://i.imgur.com/YgEjUuI_d.jpg?maxwidth=640&shape=thumb&f...</a><p>2. <a href="https://old.reddit.com/r/dredmorbius/comments/2w618r/how_to_kill_your_google_account_access_it_via_tor/" rel="nofollow">https://old.reddit.com/r/dredmorbius/comments/2w618r/how_to_...</a><p>3. <a href="https://old.reddit.com/r/dredmorbius/comments/3mo7l6/that_google_identity_thing_again_who_are_you_is/" rel="nofollow">https://old.reddit.com/r/dredmorbius/comments/3mo7l6/that_go...</a><p>4. <a href="https://social.antefriguserat.de/index.php/Goals" rel="nofollow">https://social.antefriguserat.de/index.php/Goals</a><p>5. <a href="https://www.nytimes.com/2016/12/13/us/politics/russia-hack-election-dnc.html" rel="nofollow">https://www.nytimes.com/2016/12/13/us/politics/russia-hack-e...</a>