I think usually the reason indicator/strategy salespeople want to hide their code is because customers would be infuriated if they could see the implementation. They would see instantly that they'd been duped.
Anything that is actually good and worth protecting would very likely have an implementation that few people would be able to understand anyways..
... that reasoning doesn't really generalize out to nearly all commercial digital products, where companies attempt to control what you can and can't do with them. It's not always necessarily an attempt to "dupe" people. It's about money. The people that are additionally duping you are just scum.
Not to mention, the majority of duped people will have no programming knowledge, and would say "wow" at the code for an SMA anyway. So, I really can't agree with your reasoning.
You don't have to understand it to cut and paste it into the public domain. I should know... I started releasing things in open-source form so that people could study and adapt it, and the next thing I know people are posting it all over the place against my explicit wishes. If I cared about making money from the indicators, I'd have pretty much no choice but to try to protect the code. It would have nothing to do with duping people.
The following user says Thank You to Richard for this post:
From my experience about 90% of commercial indicators are free indicators with hidden settings and colors and changed names.
Take a SMA, rename it into HolyGrailLine, change period setting to 43, add "cool" template with nice looking colors and sell it for $1500. I bet someone will buy it.
But don't forget to protect the code so it will be "harder" to figure it out that it is really SMA.
I am not telling that every commercial indicator is done that way.
From the other hand - if you really developped something "cool" and your product is really worth hacking, there simply no way to protect it... sooner or later it will be hacked.
The following 3 users say Thank You to roonius for this post:
Richard, I don't blame you for trying to protect your code, from what I've seen you are one of the few honorable indicator vendors who actually writes code and comes up with original ideas.
I was only making a generalization based on my experience which is like that of roonius, that most indicators are either repackaged open source code or extremely simple code masquerading as something complex. Most of them probably have 10x more time spent developing marketing material than the actual products themselves, sadly..
The following 3 users say Thank You to sefstrat for this post:
... this is the part that just doesn't match up with my experience. I've coded up stuff for a number of vendors, and not once has any of them told me they were concerned about people figuring out how simple their stuff was. What they all have been explicitly and persistently concerned about was keeping people from sharing their code without getting paid.
I think people with programming ability tend to project their knowledge onto the average consumer. In my experience, you could show consumer Joe the code for your "special" SMA, and even show them the standard Ninja SMA code for comparison. You might lose the customer, but it would be because of boredom and not outrage.
I agree with that, too, but at least for now you can still get plenty of honest people to pay even if a pirate version is out in the wild. In a few years, as children of the internet become the consumers, it will be interesting to see if that's still the case.
True, however it only takes a few knowledgeable users to spread the word. Once word gets out on the various trading forums that some commercial indicator is a fraud or ripped from a free indicator or just not good or whatever, they are going to have a hard time finding customers.
I respectfully disagree yet again, as many indicator consumers do not frequent trading forums. People such as yourselves are relatively sophisticated, but try to remember that many many people are not like you. A lot of my past customers breathed a sigh of relief if their computer came up properly and they didn't need any help making ninja start up. As a result, the wailing and gnashing of teeth that forum participants do against outright frauds don't usually give them that much trouble.
To put it another way: Remember the time that fraud was exposed on that forum and then they went out of business because they couldn't find customers? Yeah, neither do I.
Would anyone be able to provide some guidance as to how to implement using Machine ID's to lock an indicator to someone for use?
I'm not a vendor or anything but there might be an opportunity for me to program for some people at school who don't want to learn. Not a bad way for me to make some spare cash and actually get some good business experience.
At least some hints as to the proper keywords or areas for me to try and research would be really helpful.
There are commercial products with a hardware USB dongle that are pretty 'ok' as a protection.
it gives the customer the ability to move from machine, change hardware without any problems
and he will only be able to run one instance at a time..
The usual obfuscators will not stop anybody from reverse engineering or decompiling the code.
If you link your software to the machine, you will have to be 'bothered' every time they change
the hardware, as the machine ID will change.