4 ms·
So the story is that Google built up their Chrome browser on top of work done by KHTML/WebKit projects, and now, they'll potentially try to block users that are
by megous 6y ago
So the story is that Google built up their Chrome browser on top of work done by KHTML/WebKit projects, and now, they'll potentially try to block users that are still using Konqueror from using Google services that require login?
- Symbiote 6y agoEmbrace, extend, extinguish. It's just like Microsoft in the 1990s. Any developer who values open computing (open source software or hardware, general purpose computers, running whatever programs you want, working around DRM, owning your own data) should be avoiding systems, tools, services and devices designed by companies like Google, and recommending the same to friends and family. Google does not have our interests at heart.
- kbenson 6y agoYes, they'll require this for authentication, not use. There are already ways to log into Google accounts using a trusted platform like a browser when the environment can't be confirmed. Google Cloud Shell has a mechanism like this, where it will generate a URL that you paste into a browser, and it will prompt for login if you aren't, then provide a token you can paste back into the shell utility, and then it's authenticated to perform actions on Google Compute Engine as you through shell commands. This is essentially what the embedded browser context is doing in an automated way. My guess is there's a way to manually do this already, or there will be soon. The main thing they are trying to do here is make sure the login process is secure as they can make it. I think there's a non-negligible increase in security by requiring somewhat trusted applications to make the request.
- Wowfunhappy 6y agoSo in order to log in to Google Services in a browser that isn't Google Chrome, I have to install Google Chrome?
- striking 6y agoOr Firefox, or Safari, or Edge, I believe.
- Wowfunhappy 6y agoSorry, I meant for that to be implied, but should have been explicit. This requirement locks you in to using one of the major players until the end of time.
- kbenson 6y agoOr unless there's a petition process to get another browser added. I think the criteria is "not a webview, not embedded", so if your browser isn't usable for that, or at least not without it being obvious, then maybe that browser can ask to be added? There are reasons why Google doesn't just want to allow any curl request to authenticate a user, and those are valid reasons I agree with. Do those apply to a browser like Epiphany? Probably not, but there's a spectrum along which things will fall, and people will not always agree on where those things belong on that spectrum, and some things may be initially excluded purely on popularity, but that might be an easy problem to fix. Asking is pretty low effort.
- Wowfunhappy 6y agoI do wonder if Michael Catanzaro has tried reaching out to Google. Epiphany's user base is microscopic compared to Chrome's, I'm sure, but they're also very far from a fly-by-night project. Then again, I'm not sure how he would reach out. Google is infamously hard to contact, particularly in these sorts of situations where you're a victim of the AI.
- kbenson 6y agoProbably to a dev on the team that implemented this, which might be harder to find, but is also likely to be a more fruitful conversation than some front-line support rep, as technical cases and reasons can be explained dev-to-dev.
- est31 6y ago> they'll require this for authentication, not use. Except for workarounds, I can't watch age restricted youtube videos without an account. And even for normal content, youtube wants me to log in very often. I have to decline all the time. I fear that youtube will be authwalled eventually like instagram and similar services.