They are all similar: they are dangerous when gone wrong, damage your brand, expose paying customers as if they were sad idiots and - at worst - ensure that they are ridiculed on support boards even when they have an actual problem.
Implementing such a system shows that either the programmer or the project owner in question is a smartass that thinks of himself as more infallible and better than all the others that programmed such systems that subsequently went haywire. Sorry for the harsh words, but after being bitten multiple times by such schemes, I have no nicer ones.
https://hackertimes.com/item?id=2447485 (I won't copy over my full complaint, read it there)
http://en.wikipedia.org/wiki/Copy_protection#Notable_payload... (for a very comprehensive list, but without comments about false positives)
They are all similar: they are dangerous when gone wrong, damage your brand, expose paying customers as if they were sad idiots and - at worst - ensure that they are ridiculed on support boards even when they have an actual problem.
Implementing such a system shows that either the programmer or the project owner in question is a smartass that thinks of himself as more infallible and better than all the others that programmed such systems that subsequently went haywire. Sorry for the harsh words, but after being bitten multiple times by such schemes, I have no nicer ones.