4 ms·
They have already done this with Chromium Embedded Framework (CEF) which I use in my everyday browser. Since it can't do logins, even things like Google Groups
by kodablah 6y ago
They have already done this with Chromium Embedded Framework (CEF) which I use in my everyday browser. Since it can't do logins, even things like Google Groups fails auth and I'm forced to use Chrome instead of Chromium.
It is very annoying, Google announced it well ahead of time, but in general just doesn't care. They suggest the browser integrate with external auth options as if I want to customize my browser for Google auth.
They're actively fighting certain user agents with secret heuristics after having people create/need Google accounts for lots of things. Bastards.
- Google234 6y agoJust use a normal browser then. You aren’t blocked from the web.
- Wowfunhappy 6y agoBut Chromium is a normal browser!
- haneefmubarak 6y agoChromium is, but the GP said they were using CEF embedded in another browser, which is specifically what this tries to prevent. I imagine using normal raw Chromium will continue to work just fine.
- Wowfunhappy 6y agoOh, oops, good point! I saw the line "I'm forced to use Chrome instead of Chromium" and made some assumptions! If Google wants to explicitly block a framework that is designed to be a WebView, that seems a bit more reasonable (even if it sucks for the OP).
- Arnavion 6y agoHow would Google differentiate between Chromium and CEF in a way that isn't trivially spoofable by the latter?
- Wowfunhappy 6y agoBy doing weird fingerprinting stuff, I assume. I dunno. I think the situation where a company made a framework explicitly for embedded WebViews is a little different than what's happening with Epiphany.