There are many arguments against this but not many brought the implications for search engines. If websites implement this, it will effectively make building a web search engine impossible for new entrants. The current players can whitelist/attest their own clients while categorizing every other scraping clients as bots. If not for other reasons, I can't see how Google a search company can be allowed to push somethin…
How would this work against scrapers that are based on driven anpproved browser instances, eg. something like Selenium?
Google is already pushing WEI into Chromium
751–760 of 876 posts
Re: Google is already pushing WEI into Chromium
#752Earlier quoted context omitted.
Less than 5% of global usage [1], and no presence whatsoever on mobile. Pretty much dead. [1]: https://radar.cloudflare.com/adoption-and-usage And CF stats doesn't depend on JavaScript.
4% of global browser usage can be described in many ways (defeated, miserable, collapse compared to the past etc) but it definitely is not dead and is one of few developed browsers.
Re: Google is already pushing WEI into Chromium
#753Earlier quoted context omitted.
Microsoft was the same, and still they were humbled into opening the space for others (with the browser-choosing screen at first boot). If people are noisy enough, lawmakers can be distracted from their payola.
That was in 2001. It wouldn't happen today - see Apple and their walled garden.
Re: Google is already pushing WEI into Chromium
#754Re: Google is already pushing WEI into Chromium
#755Get the Wikipedia Foundation on board and make sure the wikipedia or other big mediawiki hosts refuse to show any kind of content if such feature is detected in the browser. Also, if you're a distro mantainer, configure apache and nginx defaults to make this is the default behaviour. Even better: instead of redirecting to any wall of text with a long explanation of the political and technical reasons of this choice,…
However, I think the other stuff that you had mentioned would be OK.
Furthermore, a distro maintainer could configure clients by default to disable WEI (or to not include client programs that have WEI).
Re: Google is already pushing WEI into Chromium
#756Earlier quoted context omitted.
"We" already waged a grassroot browser-war campaign in the late '90s-early '00s, when Mozilla was born and eventually birthed Firefox. It was successful enough to seriously dent the Microsoft monopoly, creating the political conditions for antitrust authorities to deliver significant hits to their power. It can be done again. Just drop the fucking Chromium bullshit now.
While I don’t want to be defeatist the web was smaller then, we had a common enemy in Microsoft that actively made the web worse. Google makes it better for ordinary people. Or at least gives them that impression due to sites targeting chrome. Firefox was an easy sell because it was just better for the user and importantly the dev tools were a quantum leap ahead. The web was largely still made up of enthusiasts, very…
Yeah, but that also means that fines can be much bigger now, and make bigger headlines - which is what politics is about.
> Any fight back that isn’t mobile first is doomed.
This is actually a prime chance to highlight that mobile needs serious antitrust work.
Firefox on mobile exists, btw. Are you using it?
Re: Google is already pushing WEI into Chromium
#757Earlier quoted context omitted.
WEI turns non-compliant browsers into second-class citizens. You’re perfectly free to use whatever compliant browser engine and OS combo you like today – but in a world with WEI, you’ll have to use Approved Chrome on an Approved OS on Approved Hardware with Approved Signing Keys, or you won’t be able to sign into your bank.
Is there any way around this, like spoofing headers or OS specs?
Re: Google is already pushing WEI into Chromium
#758Earlier quoted context omitted.
Unfortunately Firefox doesn't have a good UI/UX after all. The last time I checked, multiple profiles support is somehow half-baked.
Multiple profiles is fully supported. It's just hidden behind a clunky UX. Also check out firefox containers which is to profiles what docker is to virtual machines.
That's part of the "problem" with Firefox's support of profiles. It feels more like an afterthought and less like a primary use case the product wants to surface. To approximate the functionality Chrome has, I had to bookmark "about:profiles" and make it my home page.
Chrome also added this nifty feature that lets you open links as a Profile, making it easy to switch.
These may seem like small issues, but the end up mattering.
Re: Google is already pushing WEI into Chromium
#759Re: Google is already pushing WEI into Chromium
#760Earlier quoted context omitted.
Multiple profiles is fully supported. It's just hidden behind a clunky UX. Also check out firefox containers which is to profiles what docker is to virtual machines.
Containers are useful, but it's like having a few similar terminal windows open. Eventually you'll type something on the wrong window... at least I found myself searching for personal stuff on my work Google container. With profiles I can have different bookmarks, extensions, and even a different theme so I'm aware I'm on my personal profile, not on a work profile. Since switching profiles on Firefox + macOS is a pai…
This, so much. Anytime I've brought up profiles on Firefox, I'm told about this alternative that isn't a replacement for the feature.
Safari is (finally) bringing this, so maybe the folks at FF will begin to see this as a feature worth investing in. First-class profiles support is one of the main reasons I stick to Chrome, despite trying to switch.