Just wondering if I could run some thoughts by you.
I am about to release a DLL for a target client base and obviously you get people who will distribute this amongst dodgy channels.
I have setup my site to provide download links via user accounts and each dll is serialed in some way internally. So, I'll be able to track the source of the Buccanneer (Pirate gag )
I am wondering, should I also add an internal 'kill switch', so the DLL communicates back to a server to see if it is 'valid'. Ie. kill the leaked DLL's?
I was thinking of doing this in an unitrusive fashion, so if the DLL is not connected to the internet then it will continue working. But if it is connected and deemed 'not valid' the DLL will fail. Obviously, I want to do this in a way that is 100% non-intrusive to the end 'legit' user.
Although this method isnt perfect, it should slow down the piracy rate. And yes, if someone really wants to they can crack the DLL.
I just dont want the 100's of hours I have put into this go down the drain (being a solo dev). I am sure you'd understand
I also don't want to charge alot for my work, thinking around the $10-$20 region. I could charge more, but that is not who I am. I want people to enjoy the DLL as much as I have enjoyed making it. And so far the feedback from the 'target' has been awesome.
Thanks in advance