Ways to prevent leaking?
Hello,
i hope soon to get my script out on gmodstore, which is an administration tool that works on both a website and on a server.
Me and my partner already designed a license key system, and integrated that into the web panel, since that is much easier to hide.
Since my server-side code does not neccesarily require the web server to be online(if a server's website is down but their server is up, they can still resume their administrative stuff) i was wondering how i can secure that aswell, without hindering the server owner.
I had the rough concept of doing a post with the string replacements gmodstore offers you, and if the steamID is in our database and the key the user entered in the config belongs to said steamID (steamID of the person who purchased) and if said key is not in use already on someone's website, the script will download an important function to run.
I have read several threads on DRM's, which alot of people do hate. But i really do not want weeks of work to leak. I was wondering if anyone else had better idea's of preventing leaking or something like that.
Going with your own DRM is your option; Freeman does it and a few others as well, and it seems to work for them. But here's what I've noticed.
I used to run DRM on my scripts, but I ended up taking it out because well A) Users don't like that B) Especially on the Lua-side, it's going to get cracked eventually.
It's Lua. Your only hope is to apply DRM to the web-based stuff. And maybe some type of just monitoring functions to the Lua. I've found that Gmodstore sort of acts as a great way all in its own, because let's face it, not all people who utilize scripts are the smartest cookies. And a person using a leak is going to need support SOMEWHERE down the road. And you're going to be able to tell if that person has purchased your script through gmodstore, and if they haven't, well, don't give support. Eventually, they are going to have to buy that script if they want the support and the ability to get updates.
Most people who use leaks are the kids, who have no source of income. Most those leaks are out-dated, and as soon as you release an update, all the leaked copies become old. And everyone wants the latest and greatest copy of a script, especially if they are going to run a serious server, and they like the product enough.
I've had NUMEROUS people who have come to me and said "I started out with a leaked copy of your script, but I needed support, and I liked your script so much that I scraped the money together so I could buy it".
So having leaks, aren't ALL that bad. Some people use leaks as a "try before you buy". And MOST of the time, it works out well.
Now again, this isn't to say that you shouldn't protect your work, DRM on the Lua side for me, just was more hassle than it was worth, so I just stopped DRM'ing stuff. Your best bet, is to probably try and put something into the web-panel side.
Maybe Freeman or someone else who uses DRM on their Lua stuff can give some insight of alternative methods, or an approach you can take.
Hey, just a quick note.
I agree with Richard, but it might be a bit simplifying the situation.
There is a reason why I did not use DRM for a long time. I would not put a DRM on a completely new brand. Leakers and leak users is an extremely good way to advertise your product, if you do it smartly.
When I still had some free time, I tried out several methods to manipulate leakers and leak users of my work. But at certain point it became impossible due to the shear amount. I also got harrased, blackmailed, doxed pretty much daily by random kids who thought they were a bigshot. And since I've already almost finished my AutoUpdate system I've added DRM as a side feature.
In the end, benefits of fully automated updates (Release patches almost daily), data sync, language sync, vehicle tickets, etc far outweight the negatives of an included DRM. People are more than happy. Plus it allows me to know who was to blame for the leak and if the owner itself was not to blame I could whitelist his servers.
So, my advice would be: do not add any protection to your addon atleast for now. Let the leaks spread, then take them down slowly (not all at once) to give some challange to leakers to increase the demand and by that the potential value of your addon in the eyes of leak users. Logic being: the harder it is to get while people try, the better it must be. Also be sure to push out regular updates making the previous leak pretty much useless, giving even more challange to the leakers.
After certain point publicity will increase automatically and this won't be needed anymore (500 sales or so). Nows the time to implement atleast some kind of protection. This will tripple your sales for the next week or so.
There is a bit more to it. But these are the basics and is what I would do if I would be just starting up. It would also deal with the "Most people who use leaks are the kids, who have no source of income." issue. The "Try before you buy" thing isin't that great in garrysmod. People don't "buy" after trying since there is hardly any incentive.
So, as Richard said: "So having leaks, aren't ALL that bad.", which I completely agree with. I think this is the sole reason why VCMod got so popular. I was persistant like hell with these tactics.
Sorry for the long post, I like procrastinating..
ByRichardat 9th of July 2017 10:47:07
Going with your own DRM is your option; Freeman does it and a few others as well, and it seems to work for them. But here's what I've noticed.I used to run DRM on my scripts, but I ended up taking it out because wellA) Users don't like thatB) Especially on the Lua-side, it's going to get cracked eventually.It's Lua. Your only hope is to apply DRM to the web-based stuff. And maybe some type of just monitoring functions to the Lua.I've found that Gmodstore sort of acts as a great way all in its own, because let's face it, not all people who utilize scripts are the smartest cookies. And a person using a leak is going to need support SOMEWHERE down the road. And you're going to be able to tell if that person has purchased your script through gmodstore, and if they haven't, well, don't give support. Eventually, they are going to have to buy that script if they want the support and the ability to get updates.Most people who use leaks are the kids, who have no source of income. Most those leaks are out-dated, and as soon as you release an update, all the leaked copies become old. And everyone wants the latest and greatest copy of a script, especially if they are going to run a serious server, and they like the product enough.I've had NUMEROUS people who have come to me and said "I started out with a leaked copy of your script, but I needed support, and I liked your script so much that I scraped the money together so I could buy it".So having leaks, aren't ALL that bad. Some people use leaks as a "try before you buy". And MOST of the time, it works out well.Now again, this isn't to say that you shouldn't protect your work, DRM on the Lua side for me, just was more hassle than it was worth, so I just stopped DRM'ing stuff. Your best bet, is to probably try and put something into the web-panel side.Maybe Freeman or someone else who uses DRM on their Lua stuff can give some insight of alternative methods, or an approach you can take.
A) Users don't like that
Only when they notice it.
The best plan is to make "1 downloaded copy is linked to one server ip".
gmodsecure