Blank check terms, Runtime kill switch - twin EULA problems

[Curry Kenworthy]

A New Year summary -

Good holiday discussion on a common threat to LiveCode users!
That requested feedback helps LiveCode re-evaluate extreme plans.

We have successfully raised the topic. Now anticipating a response ...

Don't get distracted -

 From the entire LiveCode Create EULA and FAQ,
I chose the 2 Extreme risk clauses endangering everyone:

- 8.2/3.3 Runtime kill switch = fragile Toy Apps.
- 8.1 Blank check terms = legal/financial minefield.

Many different projects, budgets, and features,
but these are what can unite us; the risk is global.

Don't get redirected -

Not just a personal, private account matter - 2 global flaws!
Can't reliably plug in your numbers while the terms are broken.

A real fix is needed; not just emotional persuasion techniques,
presentations, personal favors, and threats to like it or else.

Don't settle again for a soothing/chipper/forceful tone of voice;
Window is closing to actually fix these problems.

Twin clauses, Extreme risk -

8.2/3.3 Runtime kill switch = fragile Toy Apps.
Subject to renewal, whim, outage, closure, or glitch.
Instant disaster! Loss of built products and users.

8.1 Blank check terms = legal/financial minefield.
All subjective. You pay whatever they say.
No protections; this can bankrupt or derail operations.

Not only commercial users. Anyone.

Too dangerous to accept EULA with these, and I realized
it would be immoral not to warn the rest of you! So I did.

No legitimate purpose -

You can't gain more HONEST money with a Blank check.
You can't MORALLY or SAFELY leverage users with app kill switch.

LC data hosting of course is another matter/choice.
Not a downside. So let's ensure they are thoroughly removed!

No excuse for Runtime kill switch and Blank check terms.
It's a bad look, gun to head; both are extreme and dangerous.

Meet the LiveCode Create EULA -
https://livecode.com/eula

An evaluation said "you should NOT accept this as-is" -
I agree; impossible until several issues improved.

Runtime kill switch ...

The EULA keeps mentioning 'access' to built apps.

"3.3 ... Violation of this clause may result in the suspension
of access to the LiveCode platform and your Created Software."

"8.2 ... LiveCode Ltd reserves the right to withdraw the granted
licensing and remove access to any apps built using LiveCode Create"

Kill built apps? This is nuclear!

Can:

- Break production systems.
- Strand/lose apps and end users.
- Trigger contractual breaches for you and end users.
- Disrupt your development, business, hobby, life.

This is unacceptable Extreme risk; No excuse, never safe in EULA.

Proving my point, the FAQ indicates arbitrary use,
without any actual 'violation.' Never safe in EULA!

Meet the LiveCode Create FAQ -
https://livecode.com/faq

"Apps require active [LiveCode Create] licensing to run.
If your license lapses, your apps will no longer be licensed
and they will not continue to run."

"apps... periodically look for a connection to check their licensing."

1000 ways to trigger disaster - LiveCode ends, you are ill...
 From bad weather to banking, health or human/software error.
Much more so than just using hosting or data. Never safe.

Opportunity -

Popular alternatives have come a long way.
People have been retooling elsewhere; no choice.
But they do want a solution here!

Next time - Blank check terms summary, Managing risk meanwhile.
I enjoyed the holiday discussion.

LiveCode recently requested my feedback to help improve LC.
Glad to help. Easy to fix, if LiveCode chooses.

Bright future / new year...

Best wishes,

Curry Kenworthy