Follow

"We are shutting down Google+ for consumers"

"90 percent of Google+ user sessions are less than five seconds"

blog.google/technology/safety-

@fribbledom those five seconds are comprised of someone accidentally logging into Google+, cursing, then immediately logging off.

@somarasu @fribbledom the only thing I liked about G+ was the ability to easily share to a subset of followers. I know masto has "post to list visibility" on it's feature request list, and I really wish I knew enough about rails to implement it, cuz I think it would be useful

@fribbledom I mean to be fair most of the time when I get on Mastodon I stay on for just long enough to say something completely random and boost some random toot

@InTheLandOfTheRisingSun

That one clearly took you more than 5 seconds to type out 😆

@fribbledom good point, but you're strongly assuming that neither of us is close to the event horizon of a black hole, which may have an effect on the passage of time

@InTheLandOfTheRisingSun Yeah, I always keep forgetting that... especially when doing my budget estimates 😂

@fribbledom

* We found no evidence that any developer was aware of this bug, or abusing the API, and we found no evidence that any Profile data was misused.

two bullets earlier:
* We made Google+ with privacy in mind and therefore keep this API’s log data for only two weeks. That means we cannot confirm which users were impacted by this bug.

they found no evidence bc they were not keeping an adequate audit log -- a cybersecurity rookie mistake. they did not build this with privacy in mind.

@fribbledom they are choosing to reveal now because of wsj.com/articles/google-expose

they've known about the bug for awhile. it existed, apparently undetected, for ~3 years. a major failure on their part that they are attempting to downplay, in my view.

COI 

@walruslifestyle @fribbledom I disagree that having an aggressive log deletion policy is a bad thing. Sensitive user data should not be kept around longer than necessary, and definitely not in log files separate from the application's main database - that's a recipe for an actual data breach rather than what we have here which is a possible breach.

[Conflict of Interest: I have worked for Google less than one month.]

COI 

@riking @fribbledom if they claim soc 2 or iso 27k compliance then they should be keeping audit logs for any external access to information that needs to be secured, precisely so that they can determine the nature and extent of data breaches like this one. it's a major fail on their part, imo

@fribbledom I'm only ever reminded of Google+ whenever I enter a beta test for an app on Google Play and they link me to their Google+ page for bug reports or whatever.

I have no idea why that standard exists, but it does. And I hate it. Google+ is and always will be a failure. There's plenty of good sites that can host that stuff.

@fribbledom maybe G👀gle should go back to supporting an open ecosystem and standards like #XMPP...

Maybe put "Don't be evil" back into their company vision 😠

@fribbledom And no fines or penalties will occur. Business as usual.

Long text, informatics gushing 

@fribbledom

I'm, losing my mind laughing at this. This is a UXd nightmare.

I felt, (like most people clearly) that google+ was terrible, especially since youtube forced me to adopt it. But I could never imagine building a platform that fails the 5 second test 90% of the time out of such a huge sample of user, that's fucking legendary. That's an ACHIEVEMENT.

@fribbledom I read that and thought "no way, there's no way people are bouncing that quickly." So I went to my google plus homepage and...yeah, there wasn't even five seconds' worth of content.

@fribbledom And thus, myself, and many others have been finding refuge here on Mastodon. :)

Sign in to participate in the conversation
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!