3 ms·
Not really. Every piece of shrinkwrap software comes with a timer that kills itself when it isn't registered in time. In some cases, it'll even uninstall itsel
by dismantlethesun 10y ago
Not really. Every piece of shrinkwrap software comes with a timer that kills itself when it isn't registered in time.
In some cases, it'll even uninstall itself or its core 'premium' components. In others, it'll simply stop displaying information and ask for payment.
Obviously, you couldn't do such a thing if you're a web designer... but if you're a developer, writing a plugin for their CMS or the such, then including a security file in your codebase is a-okay.
And if they call it "work for hire" and attempt to sue you, remind everyone that if you aren't paid then you aren't hired... as per your contract.
- Bluestrike2 10y agoIt's different when the customer knows about the timer and agrees to it somewhere in the EULA. It's when you hide that security file, or go back in and do something, that you're stepping into a whole new pile of shit. A lot of PHP software (forum software like vBulletin, CMS's, etc.) have phone-home or license verification mechanisms. That's usually fine, unless you whip up something nasty that does something beyond just disabling the software in question.