I do know many plugin suppliers restrict the variety of activations to a sure variety of domains however I’m questioning how it’s achieved and why it can’t be bypassed.
Within the strictest of senses it is a violation of the GPL, the code itself is free and you may distribute it on all of your websites. That is not the identical because the code functioning although. Nothing stops a buyer getting auto-updates on one web site then copying it themselves to their others, and this is not one thing you’ll be able to shield towards through code licenses as it is a elementary GPL freedom. Likewise with code modification.
In the usual licensing mannequin, what stops a consumer from utilizing the identical license on limitless domains?
Nothing, the consumer can edit the code and delete the licensing features if they need, they’ve the fitting to take action in line with the GPL license.
Remember that any code ought to be GPL suitable. Should you disagree that is your proper however you’ll have to show it in a courtroom of legislation, and may seek the advice of applicable authorized recommendation. The principle WP neighborhood holds that WP code must be GPL although and your disagreement might result in boycotts, blackballing from WP occasions, and barring from the WP plugin listing and neighborhood efforts. As a software program vendor it is a very excessive worth to pay, particularly if you wish to entice massive firms and businesses.
If my server is predicted to confirm which area the request is coming from, cannot a consumer spoof the area by altering a number of strains of code in WordPress?
Not in case your server sends its verification again through a webhook. This manner the plugin by no means will get the affirmation code it wants again if it tries to spoof the area, however this does not actually work anyway, and it is not one thing a pirate would do. It is a lot simpler to vary the code that checks together with your server to all the time say “sure” with out bothering to make the request, both by modifying your plugin/theme or through filters/proxies.
This can be a cat and mouse sport, and there may be all the time a path to escalation. You’ll by no means defeat a decided pirate, it doesn’t matter what licensing scheme you implement, it doesn’t matter what code license you select.
The one methodology folks have found out to reliably keep away from this stuff is to implement their product as a subscription service and transfer some performance into the cloud, and sue copycats for trademark and model infringement.
Essentially, the worth isn’t within the code you promote, however within the assist providers and continued updates that you just as the vendor/vendor present.
