11–20 of 207 posts
How does WEI work with non-browsers, like curl or python requests? I was wondering if there is some motive here to monopolize web scraping (especially with respect to harvesting AI training data)?
EDIT: Saw a few mention two solutions to disable the automatic verification on iOS & macOS.
https://blog.cloudflare.com/how-to-enable-private-access-tok...
How does WEI work with non-browsers, like curl or python requests? I was wondering if there is some motive here to monopolize web scraping (especially with respect to harvesting AI training data)?
it doesn't. Hosts will inevitably start blocking clients which don't exchange an attestation token
So, how can this be bypassed in theory? Any ideas? Brainstorming is allowed. EDIT: Saw a few mention two solutions to disable the automatic verification on iOS & macOS. https://blog.cloudflare.com/how-to-enable-private-access-tok... https://support.apple.com/en-us/HT213449
So, how can this be bypassed in theory? Any ideas? Brainstorming is allowed. EDIT: Saw a few mention two solutions to disable the automatic verification on iOS & macOS. https://blog.cloudflare.com/how-to-enable-private-access-tok... https://support.apple.com/en-us/HT213449
How does WEI work with non-browsers, like curl or python requests? I was wondering if there is some motive here to monopolize web scraping (especially with respect to harvesting AI training data)?
Instead of simply flailing our collective arms around complaining about an evil corporation, has anyone written to the respective competition authorities (such as the FTC in the US or CCI in India) about the potential anticompetitive effects of this proposal?
The link to Yoav Weiss's blog is great. --- start quote --- So, you don't like a web platform proposal ...you may feel that your insights and experience can be valuable to help steer the platform from making what you're sure is a huge mistake. That's great!! Getting involved in web platform discussions is essential to ensure it's built for and by everyone. ... In cases where controversial browser proposals (or lack o…
There's two aspects to that actually. 1. Often the feedback goes completely to the wrong address. You won't stop Google from doing google things. 2. Most often the depth level at which the discussions on web standard are made will alienate most people, so instead of participating in "standards making" they turn somewhere else (1.). The web is awesome and it got awesome because for the first 15 years of its existence…
It also takes a lot of time. You have to read quite a few proposals, and there are literally hundreds of them, you have to participate in discussions in the GitHub issues, on the w3c mailing list, and in multiple face-to-face discussions.
Even the most technical people find this daunting because they are not paid for this (unlike the people making and promoting the specs). So even the technical people often come into an issue, voice their concerns briefly (or not-so-briefly) and are summarily dismissed.
I've seen Google engineers misrepresent and ignore any input from engineers working on Firefox and Safari, and just push their specs forward. So what chance does an outsider have?
It's a mess.
Granted, it's a better mess because so many discussions are happening in the open unlike 10-15 years ago, but it's still a mess.
Soon, websites will require kernel access to make sure you don't have cheats installed. (Sarcasm, obviously)
Not that extreme but some banking apps on android did check for root at some point and refused to run so there may be precedent