Live data from Hacker News

www.google.com – The page is blank when accessed

github.com

101–110 of 320 posts

Re: www.google.com – The page is blank when accessed

#101
Just another "oops" from Google against Firefox.

"Over and over. Oops. Another accident. We'll fix it soon. We want the same things. We're on the same team. There were dozens of oopses. Hundreds maybe?"

https://www.zdnet.com/article/former-mozilla-exec-google-has...

Re: www.google.com – The page is blank when accessed

#103
post #16

Earlier quoted context omitted.

Our bad reputation is not entirely undeserved, some of us are not as well behaved as others.

[flagged]

A bit of searching suggests that this individual is the same 'robertsdotpm' who posted that "b-bazinga" comment, or at least is closely associated with them.

Re: www.google.com – The page is blank when accessed

#104
This is a good reminder that readers of HN should take to heart: Just because a popular github issue gets posted to HN doesn't mean that you should head over and do your posting there. Keep it here, usually the associated experts are already on their way or busy working on the problem and you are not helping.

Re: www.google.com – The page is blank when accessed

#105
post #4

9 minutes ago: > Since this has now been posted to HN, I'll be locking this thread. This bugtracker is a work place, not a discussion forum. We have a bad fame.

> This bugtracker is a work place, not a discussion forum. that's actually an excellent way to frame what a bugtracker is actually for. it is about workers getting shit done and its optimized for the people who work the issues. it isn't optimized for the people posting comments on issues. and the fact that a lot of users that have never had to deal with fixing software bugs think it looks like a forum website would e…

> it is about workers getting shit done and its optimized for the people who work the issues.

The above phrase also explains why Social Media is not a bug-tracker. ^_^

Re: www.google.com – The page is blank when accessed

#106
post #16
post #4

9 minutes ago: > Since this has now been posted to HN, I'll be locking this thread. This bugtracker is a work place, not a discussion forum. We have a bad fame.

Our bad reputation is not entirely undeserved, some of us are not as well behaved as others.

[flagged]

Re: www.google.com – The page is blank when accessed

#107
post #97
post #93

Another reason to stop using Google. Don't waste the opportunity! Switched to DDG ages ago, and even though it's not amazing, it's already better than Google. Although, if we're honest, searching these days is absolutely atrocious everywhere. Any keyword search will only net you ads or "top X" articles full of SEO garbage most likely written by AI at this point...

For people who don't know them yet: use DDG bangs. For example "!m restaurant [citynmae]" will immediately bring you to Google maps, "!w chemistry" will open Wikipedia etc. Super easy and powerful :)

Setting stuff up for that in any browser worth it's salt isn't too difficult, skipping the entire middleman of any search engine.

Re: www.google.com – The page is blank when accessed

#108

Earlier quoted context omitted.

They probably did. However wanted to screw Firefox users the same way as the YouTube slowdown.

There's a much easier explanation. They didn't test on it at all. It's a browser with sub-5% market share. There are folks in Google who personally test on firefox and believe in it ideologically as an important peace of the web ecosystem, but that's not a company policy and detecting Firefox bugs does not gate feature release for most projects.

That's just sabotage with extra plausible deniability.

Re: www.google.com – The page is blank when accessed

#110

Google is tracking the incident here: https://status.search.google.com/incidents/hySMmncEDZ7Xpaf9i... Disclosure: I work at Google but not on this. This was linked from the Bugzilla bug.

What I don’t understand is why this isn’t just a rollback, or at worst a revert commit and redeploy. I can forgive an issue with a slightly obscure browser, but the fix should be trivial for Google engineers?
Post reply on HN