Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

1. I am a human. I promise :)

2. I apologize if my response came off as “PR speak” as that was not my intention.

3. I am trying to manage customer concerns. It’s why I’m responding on HackerNews and similar sites.



As no one else has, I am going to thank Seth for making the time to comment here. He didn't have to, and as he just said, he is human too.


> I am trying to manage customer concerns

You do that by providing actual information, not by corporate zero-information talk.


You do realize he has to run the information he can and cannot give out by his higher-ups and possibly legal before he can reply publicly, right? Google isn't a small operation and is very vulnerable to lawsuits.

Also it's a Sunday.

The fact that he's even publicly responding here personally is already surprising to me.


As mentioned elsewhere in the comments they are still working on actually fixing the issue.

They have already acknowledged it, given some details about what they believe to be the root cause, and implemented a band-aid fix for the time being. I'm sure once they have fully investigated and resolved the issue they will provide more details.

At this point, giving out details based on what they think is the issue now may end up being partially or even fully incorrect and that doesn't do anyone any good.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: