Earlier quoted context omitted.
Thanks for your feedback. The whole explanation can be found about cookies can be found here. Tell us what you think! http://tos-dr.info/topics.html#cookies > 5 GitHub requires cookies 5: means it's a low score. So it's considered bad, but it doesn't influence very much the whole class of GitHub. > GitHub requires cookies to work and misleads you to > believe that you remain anonymous while cookies contain > “unique…
Not to be a stickler, just trying to help, but persistant is misspelled (persistent).
ToS;DR — TL;DR for Terms of Service and Privacy Policy
121–130 of 131 posts
Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy
#122Fantastic to have. It is really hard for companies to offer simply legal terms, since any simplification starts to undermine the actual detailed terms. Awesome to have this from a third party. I imagine this would be particularly valuable as a browser extension.
Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy
#123I have been thinking about doing something similar for quite sometime now. Specifically I wanted to build a browser extension that highlights only the important parts of agreement. And the important points will in turn be decided by the community of users with the system keeping track of different versions of agreements and data of interest in it.
Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy
#124I have been thinking about doing something similar for quite sometime now. Specifically I wanted to build a browser extension that highlights only the important parts of agreement. And the important points will in turn be decided by the community of users with the system keeping track of different versions of agreements and data of interest in it.
This is a great idea. The extension can be something like DIIGO does - highlight parts of the agreements that are deemed important or critical to consumer + provide snapshots of the TOS/Privacy policy whenever there are changes.
Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy
#125This is awesome! It would be cool if this could be turned into a browser plugin so you could see what class site you're visiting.
Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy
#126An API and chrome addon would be very nice. I wouldn't check the site, but I would like warnings when I accessed the registration page of a bad website.
I noticed that it's under the AGPL. That might be an issue for developing a Chrome plugin.
PS: hey Ben!
Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy
#127An API and chrome addon would be very nice. I wouldn't check the site, but I would like warnings when I accessed the registration page of a bad website.
tossos.com was built about 6 months ago. Trying to do similar things as this. It has a Chrome Plugin... check it out.
Let us know what you think!
Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy
#128Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy
#129It seems idealistic, but a service like this would be incredibly insightful. I only "read" (read: skim) the TOS of a select few companies (Apple, for one), so the high-level summaries shown on this landing page are immensely valuable (though the scoring system seems obtuse). Of course, now one has to worry about the objectivity of the summarizers.
Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy
#130Earlier quoted context omitted.
Oh please, do condescend to me about what sites I have run and which I have not, much less ones I have or have not written myself. Look, I (and likely many others here) know what you're talking about, and it's not necessary. You can deactivate things, sure, but you can also say "This cannot be undone," and people will know what that means . Software has commonly operated this way for almost the entire GUI era (at lea…
No condescension intended. Sorry if it came across that way. I can only throw in my experience, which is that users of the sites I run have a history of not understanding what it means when they hit the delete button, regardless of how many warnings you give them. As I said, it's a trade off. The upside for the site owner is less headache and angry users. The downside, at least in my experience, is nothing (apart fro…
You'll pay less for storage, too.