| ▲ | SoftTalker 7 hours ago |
| Using a maintained and up-to-date browser is a reasonable requirement for an IT department (should be for anyone really). Would you suggest they should be allowing IE6 just because a user might prefer it? Of course Google is going to suggest using Chrome, if they detect that the browser might be out of date. |
|
| ▲ | dijit 7 hours ago | parent | next [-] |
| Is the implication that Firefox is not maintained or? The issue presented doesn’t seem to be “an up to date browser check” it seems to be a “is it latest chrome” check, which is a very different thing. |
| |
| ▲ | SoftTalker 7 hours ago | parent | next [-] | | We don't know. The author doesn't mention how current the Firefox browser is/was. If the organization is indeed enabling a specific check for Chrome that seems a little over the top but they're the ones supporting their users and if they want to make their life easier by only dealing with one browser that's their decision to make. It's like saying that everyone has to use Windows, or a specific line of laptops, or any other standardization to simplify the support workload. | | |
| ▲ | rpdillon 6 hours ago | parent | next [-] | | > This was for a Google Workspace Business Plus account and workspace, from an up to date browser and OS. | |
| ▲ | kolinko 6 hours ago | parent | prev | next [-] | | Not a little over the top, it is anticompetitive behavior. | | | |
| ▲ | michaelmrose 7 hours ago | parent | prev | next [-] | | It's not a little over the top its an antitrust issue and clearly and obviously wrong. | |
| ▲ | SpicyLemonZest 7 hours ago | parent | prev [-] | | It's not clear to me that Context-Aware Access is as configurable as you're implying. At a glance, the docs seem to suggest that Chrome is the only browser you can force standardization on, which IMO does push this towards being Google's fault. | | |
| ▲ | insanitybit 5 hours ago | parent [-] | | That's correct, there is no way to say "only allow Firefox" in CAA because the attestations are either browser agnostic or chrome specific (as part of the managed Chrome offering that GSuite supports). |
|
| |
| ▲ | ibejoeb 6 hours ago | parent | prev | next [-] | | No, not at all. The implication is that the organization is dictating the software that employees are to use. There's nothing unusual about this. | |
| ▲ | jstummbillig 6 hours ago | parent | prev [-] | | If we are meant to believe that this is a Chrome-invasion-move, it's the least effective lever of all times. Most of the time the more plausible explanations are just the likely ones. | | |
| ▲ | dijit 6 hours ago | parent [-] | | you’d probably say something different if it were microsoft. I don’t see why I should give affordances of good will to Google here. They’re not stupid, they know that this is an effective lever to further cement full-fat chrome as the default browser for the internet. | | |
| ▲ | SoftTalker 6 hours ago | parent [-] | | Chrome was created because Google felt that the IE monopoly was hindering the advancement of web standards and improved browser capabilities. I suppose you could argue that was a different Google at a different time, but at one point they did feel that browser diversity was a good thing. | | |
| ▲ | recursivecaveat 5 hours ago | parent [-] | | I mean, they claimed to be for browser diversity when it was not them on top lol. Underdogs want the race to tighten up, 85% market leaders want to stay out in front. |
|
|
|
|
|
| ▲ | Karliss 3 hours ago | parent | prev | next [-] |
| If that's a the goal, then IT department should start by blocking user ability to install Firefox or other unapproved software not by blocking access to google workspace. Blocking access to google workspace using Firefox doesn't prevent using it for everything else. It's not like the google services are going to exploit a vulnerability in Firefox, everything else might. |
|
| ▲ | subscribed 5 hours ago | parent | prev [-] |
| Strawman argument. Firefox is maintained and up to date browser. Why did you even compare it to IE6, out of the curiosity? |
