44 ms·
Banks don't need the "anonymous" part of the WEI, just the "authentic" chain of trust as in am I really identifying a life person rather than a robot impersonat
by pipo234 3y ago
Banks don't need the "anonymous" part of the WEI, just the "authentic" chain of trust as in am I really identifying a life person rather than a robot impersonation.
Banks are lazy, they shouldn't need to rely on infrastructure of commercial app stores, blessed devices since they've already proven they could develop it themselves (chip cards, dongles, time-based one time codes, etc.).
WEI is mainly aimed at suppressing the unauthenticated noise, when reading a signal from GET requests (ie tracking) that was never meant to convey any information beyond what is asked for, in the first place.
- shadowgovt 3y ago> WEI is mainly aimed at suppressing the unauthenticated noise I'm not really seeing how we're reaching that conclusion. Suppressing GET request noise isn't any of the use cases described at https://github.com/RupertBenWiser/Web-Environment-Integrity/blob/main/explainer.md https://github.com/RupertBenWiser/Web-Environment-Integrity/...
- pipo234 3y agoSome examples of scenarios where users depend on client trust include: * Users like visiting websites that are expensive to create and maintain, but they often want or need to do it without paying directly. These websites fund themselves with ads, but the advertisers can only afford to pay for humans to see the ads, rather than robots. This creates a need for human users to prove to websites that they're human, sometimes through tasks like challenges or logins. Ie.: To make sure that ads are only delivered to actual living humans bothering them with a login, payment or CAPTCHA and heavily invest add-blocker detection arms race, they want the web client to attest that the genuine user actually saw the ad.