Given Google's size and market share, they should be fined whenever they break access to a competitor's website (e.g. Chrome update breaks access to DDG) or if their websites break in competitor's browser (e.g Google breaks on Firefox). They have more than enough resources to run automated checks on this, so it's hard to not see malice instead of incompetence in this case.
www.google.com – The page is blank when accessed
131–140 of 320 posts
Re: www.google.com – The page is blank when accessed
#132Earlier quoted context omitted.
Google provides a more basic webpage for older browsers.
And they often do that wrongly. Try typing "weather" in Firefox for Android vs Chrome for Android; a vastly inferior version is shown on Firefox. Changing the UA or using desktop mode makes the page work flawlessly.
Wow, that's very anticompetitive.
Re: www.google.com – The page is blank when accessed
#133Earlier quoted context omitted.
[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. Unfortunate…
"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."
And exactly where are the various QUALITY CONTROL testers that should've caught such a dead-simple problem like "This won't work with Google Search" before it ever happened in the first place?
Re: www.google.com – The page is blank when accessed
#134Earlier quoted context omitted.
They probably did. However wanted to screw Firefox users the same way as the YouTube slowdown.
I get why people want to assume bad faith but it's pointless, it's hard to intentionally sabotage Firefox when nobody tests shit in Firefox at Google. There's (or at least was) still an internal group of Firefox users a few years ago, but it's small, and internal tools may have poor or no support for Firefox at any given time. When I worked there I made some attempts to fix things (e.g. once Google Cloud was accident…
[deleted]
Re: www.google.com – The page is blank when accessed
#135Earlier quoted context omitted.
They probably did. However wanted to screw Firefox users the same way as the YouTube slowdown.
I get why people want to assume bad faith but it's pointless, it's hard to intentionally sabotage Firefox when nobody tests shit in Firefox at Google. There's (or at least was) still an internal group of Firefox users a few years ago, but it's small, and internal tools may have poor or no support for Firefox at any given time. When I worked there I made some attempts to fix things (e.g. once Google Cloud was accident…
To me, the fact they don't run automated checks on Firefox is in itself malicious and anti-competitive.
Re: www.google.com – The page is blank when accessed
#136Earlier quoted context omitted.
> 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. ^_^
Sadly, it seems to be the only bug tracker or method of getting issues noticed by the tech firms with the issues.
Re: www.google.com – The page is blank when accessed
#137Google 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?
It appears that the problem is related to the version string transmitted by Firefox Mobile. If they were to send an older user agent string, the issue would likely be resolved. However, any rollback would need to be implemented by Firefox, and it seems they are not at fault here.
From Google's standpoint, this issue may be considered a "new" bug, which means they need to conduct an investigation and address it. Consequently, a rollback is not a viable solution for them.
Re: www.google.com – The page is blank when accessed
#138Re: www.google.com – The page is blank when accessed
#139Earlier quoted context omitted.
The only thing that I've found that works properly for my use case (regularly switching between three locales and languages) is Kaggle with the lenses. The only thing missing is disconnecting the locale from the language so I can have proper decimal characters but still search for US-specific things. Right now, I have to chose between having 10,000.10 or 10.000,10 and what language/region I'm searching, together, whi…
I think "Kaggle" is supposed to be Kagi but was typoed or autocorrected or something? (If not and you're talkign about Kaggle the ML/AI company, please disregard) I also use Kagi lenses and it's been good, though for me the killer Kagi feature is being able to uprank/downrank/pin/block domains. Such an obvious and simple feature, such a powerful effect. There is a psychological barrier to overcome in paying for searc…
You're right of course, supposed to be Kagi, I blame it on a lack of coffee.
Re: www.google.com – The page is blank when accessed
#140Given Google's size and market share, they should be fined whenever they break access to a competitor's website (e.g. Chrome update breaks access to DDG) or if their websites break in competitor's browser (e.g Google breaks on Firefox). They have more than enough resources to run automated checks on this, so it's hard to not see malice instead of incompetence in this case.
What if it is done during testing as a beta release? If that's acceptable, Googs will just turn into one of those companies that never releases full versions and is always just in some form of beta release