Is it possible to protect the source code of plugins or have some form of authorization system? I've been thinking of selling some complex plugins but haven't found any way of doing it without piracy occuring after the sale of the first copy.
protecting source code/authorization system for plugins
Posted by Victorious on Wed 27 Nov 2013 07:06 AM — 4 posts, 19,123 views.
Philosophically, I am opposed to DRM, and that is written by someone who makes (and tried to make) a living from selling software.
In the end DRM causes more grief to your genuine customers than pirates, who will always manage to find away around whatever scheme you use.
You could conceivably use luac to turn your Lua code into object format, which would make it hard for people to change your code, but wouldn't stop them simply copying it.
All I can suggest is to make a good product, give good support, and ask for payment for it. Experience shows that maybe 1% of users will pay, so if you make something good, you will get some return if enough copies are out there.
One tactic is to sell it, but ask a small price, and explain that support will be ongoing if people pay. If you sell one copy, and 1000 are pirated, then you might with some justification refuse to answer detailed questions about it.
One technique used in various sites is to give away a fair amount, but have a more extensive "members" section where they get better support. Since you will know who you sold copies to, you might give quick and detailed support to such people, and refer others to the FAQ.
In the end DRM causes more grief to your genuine customers than pirates, who will always manage to find away around whatever scheme you use.
You could conceivably use luac to turn your Lua code into object format, which would make it hard for people to change your code, but wouldn't stop them simply copying it.
All I can suggest is to make a good product, give good support, and ask for payment for it. Experience shows that maybe 1% of users will pay, so if you make something good, you will get some return if enough copies are out there.
One tactic is to sell it, but ask a small price, and explain that support will be ongoing if people pay. If you sell one copy, and 1000 are pirated, then you might with some justification refuse to answer detailed questions about it.
One technique used in various sites is to give away a fair amount, but have a more extensive "members" section where they get better support. Since you will know who you sold copies to, you might give quick and detailed support to such people, and refer others to the FAQ.
Thanks for the thoughtful replies - if I do this i'm leaning towards not making any DRM.
Quote:
Is it possible to protect the source code of plugins or have some form of authorization system?
Everything is possible for someone clever enough, but why do you hate freedom?
Is it possible to protect the source code of plugins or have some form of authorization system?