3 ms·

Flat fee model + modify HTTP headers to allow paying users to skip intrusive crap? Like DNT but with $ attached. Unregistered users unaffected. Seamless for ev

• xxs 12y ago
  What makes you think I am not going to send those headers anyways - they are darn plaintext. Now if you have to sign and verify, it's another story but then again what stop people sharing those keys. For the record I resent ads in all their forms TV/Radio/Internet - the latter are trivially avoidable though.
  • m52go 12y ago
    There would have to be some kind of dynamic security setup so people couldn't do that. Like always-changing RSA tokens, etc.
  • tomjen3 12y ago
    It would be pretty easy to make the system work with private keys and signed headers or even client certificates. You could stop people from sharing by putting a high enough limit on how much you could access or even just from how many ips (ie only two distinct ips in any given 60 minute window) it could be access from. Normal users would never hit those limits, of course, but pretty quickly you would hit those if you shared your access tokens.
    • xxs 12y ago
      Limiting by IP is a horrid (or worse) idea as they are dynamic, esp . nowadays with free wifi access and 3G (or 4G). There are ways to implement quotas based on certs and revocation but it's too cumbersome to become mass use.
• jacques_chester 12y ago
  I've got a protocol design which includes this as a step.