这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@jcorbett-tandent
Copy link

A user should not be liable to Github simply because someone files a lawsuit against Github that in some way relates to the user's conduct. For example, let's say I create an app called, "Empowering Women," which a totally fictitious man we'll call "Donald Trump" finds offensive. Mr. Trump then sues Github for negligent infliction of emotional distress. The suit is frivolous and will be rapidly dismissed, but these terms before my modification would have required me to pay Github's attorney's fees.

The modification I've made allows for indemnification only if Github is sued because of the user's violation of the terms of service, not for any lawsuit, no matter how frivolous, and no matter how tangentially related, to the user's conduct on Github. If Github would like more protection than that, it should purchase an insurance policy, not foist liability on its users.

Jonathan Corbett
jon@professional-troublemaker.com

A user should not be liable to Github simply because someone files a lawsuit against Github that in some way relates to the user's conduct.  For example, let's say I create an app called, "Empowering Women," which a totally fictitious man we'll call "Donald Trump" finds offensive.  Mr. Trump then sues Github for negligent infliction of emotional distress.  The suit is frivolous and will be rapidly dismissed, but these terms before my modification would have required *me* to pay Github's attorney's fees.

The modification I've made allows for indemnification only if Github is sued because of the user's violation of the terms of service, not for any lawsuit, no matter how frivolous, and no matter how tangentially related, to the user's conduct on Github.  If Github would like more protection than that, it should purchase an insurance policy, not foist liability on its users.
@elaine-jackson
Copy link

I agree with this. GitHub should protect users speech without passing on a bill to the user. Unless GitHub is sued because a user wrote malware or something, the user should be safe.

@nsqe
Copy link
Contributor

nsqe commented Aug 1, 2017

Thanks for the suggestions.

However, while we are very protective of our users' free speech, we recognize that we can't account for every possible situation in our Terms of Service. They'd end up overbroad and unwieldy. Our goal is to set up good default guidelines that are fair to our users and easy to read.

@nsqe nsqe closed this Aug 1, 2017
@jcorbett-tandent
Copy link
Author

But this guideline is obviously not fair to your users, nor would it take extended verbiage to make it more fair. Please see the 27 upvotes this comment has received and reconsider.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants