The ionCube Encoder compiles source code to bytecode being able to obfuscate and encrypt compiled code. So far Envato is doing a great job, and I’m sure that as it grows, lots of problems arise, butĮnvato is definitely the leader in this sector, and doing a great thing.You can install ioncube to protect your php code against copy, ensuring nobody will be able to crack. Reviewers do the most of the hard job, some authors report stuff and Envato makes the adjusments, but it has to be (at some point in the future) a team of people that would work to just “keep things cleaner on Envato”. Some do piracy, some buy an AudioJungle item or get some track from somewhere and re-sell it (i’m not sure if it happened here, but I think I heard something similar on the forums)…anywayz, on such huge markets like Envato has, someone has to keep it “clean”. I was just saying that we should find a way to clean the “crumpled papers” that people leave behind on the floor in Envato Markets. Protecting small pieces of code / widgets, when you give the source code anyways, would make the customisation harder. And then when you have the messages and sections of update, check for update in your plugin, again someone will have to bother to remove them, deactivate them, or the one’s who got ‘cracked’ product will again still keep getting worried about their license, and will buy it later. As that cannon be automated, it has different logic for each plugin, not just a variable name. So, if you use the Toolkit wisely, have a license server to do the verification on the server, then it will take couple hours to crack. The ‘crackers’ are not the gods of code or something, they usually have even weaker coding skills that senior devs. They still have to take a look manually, and once again - it will take couple hours to crack it. The license activation should always happen on the license server, and it the script, whatever the ‘crackers’ would use, they won’t be able to automate that, if you do add checks in models etc. The tool is just for the starting and connecting with the API.
0 kommentar(er)
