Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

71–80 of 320 posts

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

#71

Post by oblio »

close04 wrote: post #34
jncfhnb wrote: post #13

Earlier quoted context omitted.

Some middle manager out there was making this decision. Not strategy heads

Strategy heads come up with the strategy - friction. Enough friction against Firefox will let the browser still exist (essential for the claim that there is competition) but without actually being able to compete. Middle management finds a tactic that implements the friction strategy - small "random" breaks and persistent performance issues. An engineer would find the precise measure to implement - break the UA strin…

> Middle management finds a tactic that implements the friction strategy - small "random" breaks and persistent performance issues.

> An engineer would find the precise measure to implement - break the UA string sniffing targeting a specific browser.

You got the strategy right but the implementation is laughable, sorry :-)))

The implementation is: "We have a budget of N story points this sprint to resolve bugs, let's prioritize them. Let's prioritize by impacted audience size."

The audience size will make 99% of Firefox specific bugs be deprioritized out of the current sprint. And the next one. And the one after that.

And unless a senior engineer stands up to update the prioritization criteria, plausible deniability forever.

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

#72

Post by denschub »

jraph wrote: post #59
hartator wrote: post #57

Earlier quoted context omitted.

Mozilla elitism.

Or experience with the internet? Of course outrageous GitHub issues get low quality comments from HN. The guy probably reacted like this because of the dummy comment he marked as off topic and probably made the connection. > 'now you have two problems' b-bazinga. Software engineering is hard. He might have said the same of Reddit, or any social network. It's pretty reasonable and I think he made the right call.

You are 100% correct in your assumptions. This isn't my first incident, and it won't be my last. As much as some folks here want to call me an asshole for that, we have a very good understanding of how this ends if we don't lock comments.

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

#73

Post by ben_w »

pmontra wrote: 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.

"Orange site bad" is a bit of a meme. I even heard it IRL at a hacker space in the last few weeks.

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

#74

Post by jgraham »

Uptrenda wrote: post #43
tmtvl wrote: post #16

Earlier quoted context omitted.

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

[flagged]

(I work on WebCompat at Mozilla)

There are various people whose job involves triaging issues filed on that repo, and communicating with the issue authors where necessary e.g. to figure out additional steps required to reproduce the reported problem. The point of that effort is exactly because we value reports of site breakage so highly, and want to ensure that people reporting them have a good experience.

Unfortunately when a bug report (not just this in this repo, but almost anywhere) hits (almost any) social media there's a high chance of the suddenly large audience making comments that aren't at all actionable in fixing the issue. In this case it seems highly unlikely that anyone can add additional information that will allow a faster resolution, whereas there was already one off-topic/unactionable comment at the time the issue was locked.

So if we leave the issue open, it has the downside of disrupting our normal workflows, and taking attention away from fixing either the problem at hand, or any other issues that currently require our attention. To me that significantly outweighs the potential upside of leaving it open to "make people feel welcome".

Of course, like many things in life, it's not a mathematical problem where you can derive a correct answer, but a set of tradeoffs based on experience, and therefore reasonable people may come to different conclusions.

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

#76

Post by andirk »

conradfr wrote: post #12

Funny that it works when switching to desktop mode. I never actually looked at what this does.

I think it changes your user agent string to something that doesn't say "mobile", and the device "inner resolution" or something like that to make it zoom out.

https://www.google.com/search?q=what+is+my+user+agent+string

https://www.whatismyscreenresolution.org/

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

#78

Post by yard2010 »

yunohn wrote: post #25
doublerabbit wrote: post #6

Earlier quoted context omitted.

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

Google isn’t sitting around randomly breaking things for Firefox users in this obvious way. I really feel like HNers often forget how minuscule the scale of their usage patterns are.

How convenient!
Post reply on HN