Earlier quoted context omitted.
> It's hard to describe an HTTP status as anything other than a sign. If it was purely technical, we wouldn't distinguish between 402 (payment required) and 403 (forbidden). I agree that the existence of those status codes does a good job at disambiguating representations of intent regarding payment. However, to my knowledge, there's no status code that means "Ok, as long as you don't use an adblocker". As such, any…
> As such, any such provision has to be layered on higher up the stack. The current solution is to put it in the site's terms of service. But the problem is that I never signed that TOS. We keep on coming back to this, but putting a TOS somewhere on your site is not binding. You need to get my informed consent. In the same way, if I stuck up a contract on my public blog that said "by fulfilling any HTTP request I mak…
Yep. Totally agree. Consent needs to be informed. In order for anything i'm saying to apply, the agreement must be meaningfully made. Personally, I consider a checkbox saying "I won't use an ad blocker" to be sufficient to declare that agreement valid.