From my understanding, it allows a website to check if you’re running a Chromium browser, and block your access to the site or to features of the site if you aren’t
Bing for enterprise is already blocking browsers that aren’t Edge. Clicking “Edge” from the list of browser identities in Firefox seems to go around the block.
Soon, we’ll get to “Best viewed with Chrome”, “Best viewed on 1920x1080”, “Google Chrome NOW!” even though other browsers could load the webpages just fine.
I can already picture Google down-ranking search results for any website that doesn’t implement it because obviously “if they aren’t using the integrity API we can’t guarantee they’re safe for our users”
This is the process Cory Doctorow termed “enshittification.” Services start out by prioritizing functionality for the users, even running at a loss to do so. This is one reason why new companies have a massive burn rate compared to their income.
The second step is they stop prioritizing users and start prioritizing “partners.” Those could be news sources, sellers, whatever. User functionality is compromised to optimize the “partner” experience.
Finally, they start to fuck over partners too, in order to shovel as much money as possible into the company’s accounts. Facebook did it with news sites - especially video. Twitter is doing a speed run on this. Google is accused of being well on its way with search, and I have no idea about their other services.
So, yes, Google may fuck up search just like Facebook fucked up their feed and Twitter is fucking up absolutely everything.
They’ve already fucked it up. I’ve moved on to ddg, which is something I thought I would ever do five years ago. If the ddg integration with bing goes south, then I’ll start looking into things like kagi.
The ‘average’ website wouldn’t but many of the social giants are desperately looking for a way to limit bot use. So Google gives them what they want and simultaneously gets to be the most reliable advertiser, ensuring impressions are viewed by not just a human but the right human.
Because websites will check if you have a Web Integrity token being sent along by the browser and if it cannot find one registrations and login will be closed to your instance.
Edit: And to clarify, you will not get that token unless you verify your identity within the associated google account. Hence why only Chromium browsers will support this. But it isn’t about the browser. It’s about the token.
But that token is just provided by the browser, isnt it? Can bots not run within an instance of a chromium browser? I dont get how this stops a bot account.
This goes with other changes they did to chromium. Google claims it is to prevent bots, but it really is a crackdown on ads blocking and any other “tampering” with their websites.
If you care about keeping web free, you should stop using chrome and its derivatives and switch to Firefox. They are believing that Firefox user base is low and websites can simply exclude FF and force it to implement it as well.
It’s not about whether it’s a chromium browser or not. It’s about whether a browser is “trusted” and installed from a “trusted” source, like the windows store… Basically gatekeeping. Still, Firefox and any browser could still be approved.
Absolutely! I would wager a guess that something like this would require support on a package manager level, meaning that the biggest like Ubuntu or what not could have access to a functioning “trusted” browser. But good luck on a niche distro, or if you want to compile it yourself, or if you want to use certain extensions or…
From my understanding, it allows a website to check if you’re running a Chromium browser, and block your access to the site or to features of the site if you aren’t
Bing for enterprise is already blocking browsers that aren’t Edge. Clicking “Edge” from the list of browser identities in Firefox seems to go around the block.
Soon, we’ll get to “Best viewed with Chrome”, “Best viewed on 1920x1080”, “Google Chrome NOW!” even though other browsers could load the webpages just fine.
Oh, wait.
On what grounds? I know why google wants this, but why would the average website do this?
I can already picture Google down-ranking search results for any website that doesn’t implement it because obviously “if they aren’t using the integrity API we can’t guarantee they’re safe for our users”
Which… would just de-value Google Search, no?
This is the process Cory Doctorow termed “enshittification.” Services start out by prioritizing functionality for the users, even running at a loss to do so. This is one reason why new companies have a massive burn rate compared to their income.
The second step is they stop prioritizing users and start prioritizing “partners.” Those could be news sources, sellers, whatever. User functionality is compromised to optimize the “partner” experience.
Finally, they start to fuck over partners too, in order to shovel as much money as possible into the company’s accounts. Facebook did it with news sites - especially video. Twitter is doing a speed run on this. Google is accused of being well on its way with search, and I have no idea about their other services.
So, yes, Google may fuck up search just like Facebook fucked up their feed and Twitter is fucking up absolutely everything.
They’ve already fucked it up. I’ve moved on to ddg, which is something I thought I would ever do five years ago. If the ddg integration with bing goes south, then I’ll start looking into things like kagi.
To people who know what’s going on sure, but for most users, if its not on the first page of Google it doesn’t exist.
The ‘average’ website wouldn’t but many of the social giants are desperately looking for a way to limit bot use. So Google gives them what they want and simultaneously gets to be the most reliable advertiser, ensuring impressions are viewed by not just a human but the right human.
How does this limit bot use? Is there something anti bot about chromium? Or does the api do more beyond checking for chromium compatible browsers
Because websites will check if you have a Web Integrity token being sent along by the browser and if it cannot find one registrations and login will be closed to your instance.
Edit: And to clarify, you will not get that token unless you verify your identity within the associated google account. Hence why only Chromium browsers will support this. But it isn’t about the browser. It’s about the token.
But that token is just provided by the browser, isnt it? Can bots not run within an instance of a chromium browser? I dont get how this stops a bot account.
Yeah sorry I just clarified. Read my comment higher up in the thread for more details. The token is generated upon verification of user identity.
This goes with other changes they did to chromium. Google claims it is to prevent bots, but it really is a crackdown on ads blocking and any other “tampering” with their websites.
If you care about keeping web free, you should stop using chrome and its derivatives and switch to Firefox. They are believing that Firefox user base is low and websites can simply exclude FF and force it to implement it as well.
deleted by creator
Don’t sites already do this?
browsers can currently report to be anything. which is why Google is trying to stop it.
It’s not about whether it’s a chromium browser or not. It’s about whether a browser is “trusted” and installed from a “trusted” source, like the windows store… Basically gatekeeping. Still, Firefox and any browser could still be approved.
This would be an insane damage to the Linux community since there are many different ways to install programms(including browsers).
Absolutely! I would wager a guess that something like this would require support on a package manager level, meaning that the biggest like Ubuntu or what not could have access to a functioning “trusted” browser. But good luck on a niche distro, or if you want to compile it yourself, or if you want to use certain extensions or…
What’s more trusted than source code?
According to Google - probably source code that can’t block ads and that is known to not block trackers… basically.
Or the API can die a quick death, like so many other Google products.