I interpret this as "We will try not to steal from you, but if we do, you agree that we can."owever, You acknowledge and agree that MetaQuotes does not give any warranties in this respect.
How to interpret this...
I interpret this as "We will try not to steal from you, but if we do, you agree that we can."owever, You acknowledge and agree that MetaQuotes does not give any warranties in this respect.
How to interpret this...
What these programs MAY be doing, platforms like quantopian do it openly by inviting people to develop their algos with the promise that they will be kept secret when in fact no one will ever find out in case they use them. No serious trader will put code on a program that calls home because trading is about tail risk and the tail risk in this case is someone stealing your code or even in a simple manner anticipating your orders in case you are profitable. Charting and system development should not mix but must be separated by firewall.
So for someone to pick out good from the trash is pretty hard.
You don't think the performances (backtests or otherwise) of the stuffs can also possibly be stored on the server? And searched-for by such?
I'm going to say that I think structures along that line is a much better way of structuring things anyway, as I'm currently refactoring to do it it provides your algo code some independence from the broker API. But then, my Java platform got blown out of the water by my upgrading to a new API... But, if you really want to be on the safe side, then create your entire algorithm logic in a standalone application and then create a DLL which acts as an interface/bridge between Metatrader and your Java(for example) application.
So basically: your Java algorithm communicate with the DLL(sockets, files, etc) and the DLL transmits the information further to Metatrader application. And the opposite direction also: Metatrader > DLL > Java algo...
(it was using a much earlier API).