Hello,
Is it possible to protect plugins from copying? For example, using an obfurcator and / or an external control with a verification key.
The point is, some plug-ins are complex to make, and copying from site to site without paying for a new license is incredibly easy.
To stop this scourge, can we put in place certain protections? Activation key validated via an external server, download the rest of the code after, validation, obfurcation ...
The October team could have the readable version to control the quality and non-vulnerability of the code.
Another solution would be the support of this system by the October store. I read the subscription issue with great interest. But I want to offer a complete product (as much as possible), with updated bug fixes. I am ready to make free updates and free versions in development mode. But we need to have a reflexion on a minimal system protection.
October is for DEVs, and DEVs ... well ... we're smart, and for some of us, lazy! :) Copy, Paste, and ... voila! A "free" paid plugin in a other install.
What is the position of the October team, but also of the other plugin creators on this subject?