this post was submitted on 12 Oct 2023
800 points (100.0% liked)

196

18171 readers
95 users here now

Be sure to follow the rule before you head out.


Rule: You must post before you leave.



Other rules

Behavior rules:

Posting rules:

NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.

If you have any questions, feel free to contact us on our matrix channel or email.

Other 196's:

founded 2 years ago
MODERATORS
 

🆘

you are viewing a single comment's thread
view the rest of the comments
[–] wildginger@lemmy.myserv.one 25 points 2 years ago (2 children)

On what grounds? I know why google wants this, but why would the average website do this?

[–] takeda@szmer.info 18 points 2 years ago* (last edited 2 years ago)

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.

[–] Dangdoggo@kbin.social 1 points 2 years ago (1 children)

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.

[–] wildginger@lemmy.myserv.one 0 points 2 years ago (1 children)

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

[–] Dangdoggo@kbin.social 1 points 2 years ago

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.