License TL;DR?

[frederikheld]

Hey!

I followed the rabbit hole of the license statement in this repo down to the following PDF (which appears to be the relevant one, please correct me if I'm wrong). But it's a legal document and I'm an engineer, so it left me as clueless as I was before.

Can you please give me a TL;DR of your license that states what I can and can not do with this software? Like they do on https://www.tldrlegal.com/ and similar websites.

That would be great!

Thx!

[Keillion]

Hi frederikheld,

I'm also an engineer 😊. It's not accurate in a legal, but I can give a simple answer:

This is a paid SDK for commercial use. You can directly try out the SDK for 24 hours without applying.

After 24 hours, you can apply for more trial periods in https://www.dynamsoft.com/customer/license/trialLicense.

After purchasing you can use it for commercial purposes and get ongoing technical support.

Technical questions can post here (R&D team will answer), or contact support team.

Other questions, please contact our sales team.

Support & sales teams are also available from live chat in www.dynamsoft.com.

Hope it helpful!

[frederikheld]

Thanks a bunch! It's not very clear from your GitHub repo or NPM package that this is paid software. I'd appreciate if you would state that more clearly, because it would have saved me a bunch of time.

[frederikheld]

Also a more technical question out of interest, as I have never seen your approach to open-sourcing a library that requires a license: How do you avoid key sharing or even re-writing the repo to omit the key?

[Keillion]

We do some simple verification such as domain name binding. This measure cannot prevent personal misappropriation, but it can play a very good role in avoiding commercial violations.

It is impossible to completely avoid cracking in pure js applications. Mainly based on trust.

If the license-key is found to be compromised, we also have measures to invalidate the old license-key and replace it with a new one.