zlacker

[return to "Unpacking Google’s Web Environment Integrity specification"]
1. jfoutz+KA1[view] [source] 2023-07-26 17:59:22
>>dagurp+(OP)
This kinda seems like a fantastic way to implement micro payments. The site owner sets up a attestor that knows they’ve paid.

I hate Wei in general, but it really could open up control over bots and paid access.

◧◩
2. wbobei+sC1[view] [source] 2023-07-26 18:05:37
>>jfoutz+KA1
There is no reason that can't be done with existing web technology, WEI does not advance that use case in any meaningful way.
◧◩◪
3. jfoutz+WF1[view] [source] 2023-07-26 18:18:20
>>wbobei+sC1
It provides a uniform service for ensuring a client has desired properties.

That’s kinda tricky to do well. Traffic for monitoring, you can do with a jwt, but like, enabling chunked transfer in python request lib is a problem you discover. An array of attestors could guarantee feature sets.

◧◩◪◨
4. wbobei+iI1[view] [source] 2023-07-26 18:26:41
>>jfoutz+WF1
I'm not understanding how giving the client a token that you put in a request header that proves you've paid, or is just an account lookup token to then ask a payment processor whether or not their account is in good standing, is limited in a way that WEI makes better. I don't see any use cases that wouldn't work that way that would now work with WEI.
[go to top]