Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<blockquote> <p>How do I stop users from pirating the script?</p> </blockquote> <p>Do not release sensible source code to the public...</p> <p>[<strong>EDIT</strong>] <em>After a few downvotes, I decided to comment on my answer:</em></p> <p>Any code that is released public has a chance of being hacked. This is the number one reason why Javascript is not secure. No matter how much you will obfuscate it, compress it or translate it to some random japanese dialect, it is still source code that the user has <a href="https://addons.mozilla.org/fr/firefox/addon/1843" rel="nofollow noreferrer">access to</a>. Hence it should not contain any sensible information such as passwords or such. All sensible data should be stored in the server side where it is kept hidden from the user.</p> <p>If you are releasing a php framework containing both the server and client code; then you have <em>no</em> way of <em>fully</em> protecting yourself. PHP is, like Javascript, an <a href="http://en.wikipedia.org/wiki/Interpreted_language" rel="nofollow noreferrer">interpreted language</a>. You may translate it, compress it, or obfuscate it as much as you want, (and it's probably the best thing you can do) you will <strong>never</strong> fully protect it when released to the public.</p> <p>Again... If there was a magic way to prevent code from being broken, it would have been known for a long time. No-cd patches / cracks for new games/softwares now are almost released the same day as the softwares themselves. It is, as noted by Paul, a form of flattery for you, even though I understand how sorry you may feel.</p> <p><a href="http://www.codinghorror.com/blog/archives/001125.html" rel="nofollow noreferrer">There are a few instances where programmers ended up with bullet-proof protection, but it usually involved high-end engineering.</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload