imported from 2736
https://groups.google.com/forum/#!msg/tosdr/1JPA1CuRbrc/3R9FukguTKQJ I wrote a prototype of this a few years back.
It was a Mozilla extension that added an X-client-eula HTTP header to ALL
requests which included the text of a EULA that the *USER* entered which
basically says what the user typed into their dialog box.
This is based on the logic of "*If you visit or shop at Amazon.com, you
accept these conditions.* " ...
which Amazon uses here:
http://www.amazon.com/gp/help/customer/display.html/ref=hp_200905880_conditions?nodeId=508088
In my EULA I basically said:
"By responding to this HTTP request, you accept MY conditions and your
conditions DO NOT apply."
Thoughts here?
I realize it will SUCK for the websites that now have to READ all these ToS
- but isn't this the situation they put US in to begin with?
I had an idea that if we were to standardize on a few basic ToS, the vendor
could use the hashcode of the ToS to decide if they want to respond to the
HTTP request.
Some websites and customers could BOTH have acceptable EULAs which allows
them to work together.
Another idea could be to make them machine readable so that the client and
server can both negotiate to realize that they are in agreement vs. the
problem of having to read human text which for a machine will not be easy.
Kevin
--
www.tos-dr.info // www.twitter.com/tosdr // www.github.com/Unhosted/ToS-DR
---
You received this message because you are subscribed to the Google Groups "Terms of Service; Didn't Read" group.
To post to this group, send email to tosdr@googlegroups.com.
To unsubscribe from this group, send email to tosdr+unsubscribe@googlegroups.com.
Visit this group at http://groups.google.com/group/tosdr?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
imported status as declined
Previous Title: No changes recorded
Updated Title: No changes recorded
Previous Analysis: No changes recorded
Updated Analysis: No changes recorded
Previous Status: PENDING
Updated Status: DECLINED
Previous Title:
Updated Title: HTTP request header for client-side EULAs.
Previous Analysis:
Updated Analysis: HTTP request header for client-side EULAs.
Previous Status:
Updated Status: PENDING