Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Besides protecting your NinjaScripts by assembling them as (RemoteSoft or not) .dll ...
Is there such a thing as time limit protection ?
I would like to share indicators but that after a few weeks of use, they can't be used anymore by my contacts. So that I need to send them again a new, update file.
This is the utmost control about protection for me.
Anyway to achieve it ?
Actually, I could code a time limit inside the scripts, and then protect it as RemoteSoft .dll
Is RemoteSoft viable or can it be broken ? is there a better solution out there ?
Can you help answer these questions from other members on NexusFi?
Salamander obfuscator is very hard to decompile, so coding an "ending date" in the indicator itself, and protect it is simple and efficient.
It's possible to imagine more complex solution, like creating your own license server and manage license expiration there, but complex also means expensive, harder to maintain, etc.
I don't have any specific link or tutorial about building a license server, but see it as a simple client/server:
- the client (your NT indicator) ask the server (using an or your home made protocol) if its license is valid or not.
So it can be done with some basic C# http object, or socket programming on the client side, any web server or some simple C/PHP code on the server side.
Thanks. Ninja seems to be selling some remote licencing feature but it is restricted for 3rd party developpers which is not my case (group of traders). We are just trying to prevent leak from members.
We'll start with timebased remotesoft protection and move on to licencing if ever needed. Thank you !
