Do it in software. Contract the code work out to an offshore s/w house. Don't release the source. If the potential patent/copyright owner suspects something, you are protected against their reverse engineering it by the Digital Millennium Copyright Act (particularly if you have incorporated minimal DRM into the product).
Re: Evil Designers Guide to Copying Patents
I wonder how often that happens..
Found more info on:
It happens.
Another place that patents are vulnerable is covering processes or algorithms. If the delivered article doesn't actually contain the code (object or source), how would an examination reveal an infringement?
A hypothetical example: If someone were to duplicate Google's search algorithms, but move their servers to a jurisdiction which doesn't honor US subpoenas, how could Google ever establish that the competitor had infringed rather than come up with a unique algorithm of their own? The delivered product contains no direct evidence of the process used to generate it.
Maybe use a reverse compiler, then recompile. Different burned code, no problem.
how does a college examiner detect copied answers.
Catch somebody peeking at their neighbor's paper.
Join the Discussion
Have something to add? Share your thoughts — no account required.
Didn't find your answer?
Ask the community — no account required