Live data from Hacker News

ToS;DR — TL;DR for Terms of Service and Privacy Policy

tos-dr.info

91–100 of 131 posts

Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy

#91
I like the idea and the layout is nice.

That being said, use the same categories for each company, don't re-write the description based on how good/bad it is. It would be far more useful for creating a table (which would also be a great way to organize this information, businesses looking to improve the transparency of their ToS would need only look at top scored candidates to find inspiration).

Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy

#93
post #84

Earlier quoted context omitted.

So the developers who built apps that read your FB/Twitter stream are also licensed to show the content.

Not necessary (see SoundCloud for instance). The whole problem is that the copyright license is just overbroad and not limited at all.

Partially necessary. And I completely agree with you. The licenses they demand are far broader than what they need, but that goes to the imbalance inherent in the relationship: big company with lots of money for lawyers versus some person just wanting to tell his friends what he had for lunch.

Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy

#94
Wow, this is great! I love it. Hold on, no. I hate this. This reflects what I try so hard not to be - a lazy reader.

Let me explain this reaction: The execution lacks the huge opportunity to make me, and many others, actually read the ToS we often so easily agree to. I realize there's a reference in every bullet, but it's not enough. The interface (linking to Google Groups) is terrible and not encouraging.

This is a start, but I'd argue it should serve for a greater purpose. An educational purpose, considering even us nerds tend not to read ToS. It's a lot to do with the fact we read less in the era of Hacker News (quite surprisingly - and you know I'm right), we want everything summarized. Optimize our time. But that's off topic.

Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy

#95
Given the purpose of the site and it's broad potential reach (and the fact that it's not a domain that requires pushing the envelope in terms of rich user experience), I was pretty suprised to see that the entire 'Rated Services' section was a giant white block in Internet Explorer 9.

I could understand lack of support for IE7 (or perhaps crappy formatting), would raise an eyebrow at lack of support for IE8 (given the nature of the domain and that there's no compelling reason for a lack of graceful fallback in this case), but lack of IE9 support is a bit... suprising.

I certainly hope the team plans on addressing this, otherwise you're cutting a large chunk of browser users out of the picture for (from what I can see) no compelling reason related to the technical requirements of the kind of content you are delivering.

Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy

#96
post #51

Earlier quoted context omitted.

Wait the US doesn't have an 'E'? (Is 'F' short for Fail? I thought it was just the continuation of the sequence). Regardless, at least A is best, B is worse than that, etc. which makes sense.

> Wait the US doesn't have an 'E'? (Is 'F' short for Fail? I thought it was just the continuation of the sequence) Well, apparently it's more complicated than that. I always assumed that the lack of E was so that there would be no confusion with the ESNU system (which a number of students used to have in elementary school, but then they switch over to the A-F system in middle school). Also, many countries outside the…

Dartmouth has E as well.

Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy

#97
I haven't read through all the comments but standardized and unbiased copy writing would really benefit the site. "Promise to inform about data requests" gets a plus while "No transparency on law enforcement requests" get a minus.

Both labels could be changed to "Notification of data requests", and a user would have the benefit of knowing you were comparing the same thing across multiple sites.

As it stands it's hard to compare a sites rating.

Another (possibly more prominent) example: Github has "You don't grant any copyright license to github", right below that SoundCloud has "You stay in control of your copyright", and below that 500px simply has "Ownership".

Assuming those all refer to the same thing (owning your data/copyright), a simple, "Copyright ownership" would be much clearer and unbiased copy.

Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy

#98
post #77

I'd be very careful counting the requirements for cookies as a bad thing (as seen in the github section): First-Party session cookies are a totally valid use of cookies and actually help improving the security in that a session-id in a cookie will never be copy & pasted by accident (it happens to URL-based session-id's at times) and cookies can be marked as both httponly and secure, making it more difficult to imposs…

[deleted]

Re: ToS;DR — TL;DR for Terms of Service and Privacy Policy

#100
post #68

Earlier quoted context omitted.

despite that being an important feature for any site that lets users delete their own content. Well...no. How is it important for a site that lets users delete their own content not delete it? Your statement is self-contradictory.

That's a common outlook to have if you've never run a site where users upload content. In practice, if you give your users a way to damage or delete their own account, they'll do it without giving it any thought. Then they'll think about it. And they'll want to undo it. When they don't find an "undelete" button, they'll write you an email. And if you don't have an easy switch you can flip to magically fix the problem…

I don't think you are morally correct just because you haven't gotten any complaints.

In fact, until you make it possible for people to permanently delete things, you are not. The reason you haven't gotten any complaints is that the people who deleted things on purpose don't send you an email and don't know it can be undone.

Post reply on HN