Alpha1
Well-known member
What works for me is to do a XF license token validation so that only people with a valid XF license can buy. I also require activation of the URL through the Xen Product Manager.As we know from our experience the largest problem is not with the users here on XenForo.com, that are ready to pay for a valid license, but people who purchase the add-on only to download it, install it and immediately ask for a refund and keep using the current version.
Thats a PayPal issue. Such people will not pay for your software if you have protection built into your software. They will just null it and release it on warez sites. There is really nothing that you can do to stop it. Nulled software is a fact of life. But serious webmasters will not be stupid enough to use nulled software with all malware often found in warez. If you find a site running unlicensed or nulled software, then you can always contact XF about it.but we need some mechanism not to allow this type of misuse of our services at least by majority of people who don't hack the code of the add-on, but just purchase it, activate and immediately ask for refund.
I think that its important to realize that you cant really stop unlicensed use of your software. Anything you add can and will be undone by unscrupulous people. But these people making or using warez are not your customers.
This approach does seem to pose similar risks. As soon as you have communities depending upon your server or unchecked information flowing from communities to your server, then thats problematic. An XML file on our sites that can be read by your server is ideal because it non-intrusive, does not depend on your server and we can see what information is provided.I hope this solution does not pose any risk you foresee with callbacks.