11–20 of 126 posts
Not sure if that would really dissuade anyone leaking/cracking it though, but it may possibly help determine potentially where the leak/crack came from.
There are probably many reasons why watermarking isn't worthwhile though, as you'd then need to have an 'online' system for generating new versions, rather than simply hosting a single file.
Piracy is a huge issue, one way around it, although too late for you now, is to only sell an online hosted version of your software, they can't crack what they don't have access too. Have you got a forum to engage your customers with directly? Most times (and this is a huge generalisation) but these consumers aren't 'evil', they just either have no money or don't know any better. If you can engage with them and get t…
although too late for you now, is to only sell an online hosted version of your software,
they can't crack what they don't have access too
Have you got a forum to engage your
customers with directly? First - if they wouldn't have paid anyway, you haven't "lost" anything (you've actually gained something) Second, your pricing must be turning off those who would [possibly] pay, but opt for the cracked edition due to cost Third, focus on support: you can download, install, and run OpenNMS, for example, totally 100% for free. But if you want support beyond the mailing list, you pay for it.
Old methods (90s): - turn to the law (DCMA) - prevent people from modifying code New methods: - change to a SaaS model - change the backend to an API, users order API key - ping home from your software code or every keystroke like in Windows. - free product, offer training + ads
Oh, are you equating copyright violation with major theft, murder and associated felonies so heinous that there is actually a separate body of international law to address it? Please don't do that.
Unless you are already a market leader, copyright violation is largely equivalent to an unpaid, unauthorized marketing issue. Your problem is to convert those non-paying users into paying users.
Policy:
1. Make it so inconvenient to use your software without paying for it that they decide to pay you. This is the "stick" option: you hit them with a stick until they either go away or pay.
2. Make it so easy and useful to pay for your software that they decide to pay you. This is the "carrot" option: you dangle something good in front of them until they willingly walk towards it.
Every method falls into one of those two policy groups. Think about which policy you want to use before you start making changes.
If you decide to make your software open source, you are likely to stop making money at it by selling it. However, you can still make money by consulting -- you are the world's foremost expert on this software, after all.
But piracy is good right? Death to DRM! If someone doesn't want to pay they should be able to get the content for free, then they can decide if you deserve to be paid. --- That content above seems to be very popular sentiment on HN and other techy places. I don't understand that since all you hurt are people like the author of this post. The tech community needs to get its act together and decide to support intellect…
You can't begin to understand it, if you don't understand the 'sentiment' you describe in the first place.
Nobody is saying that it is OK to steal someone's work and not pay them for it. The argument against DRM is usually that:
1. I shouldn't, as a paying customer, be required to purchase multiple times just to consume on a different platform, this increases piracy.
2. You shouldn't charge prices that your customers can't afford to pay, increases piracy.
3. DRM punishes paying customers while pirates get a better (unrestricted) version anyway, so where's the incentive to not pirate?
...and many more.
Notice how none of these endorse piracy as a good thing, merely point out that these factors lead to it.
The Coast Guard is your ally, along with the Navy. Talk to your insurance company; they have lots of experience (or else you picked the wrong one.) Oh, are you equating copyright violation with major theft, murder and associated felonies so heinous that there is actually a separate body of international law to address it? Please don't do that. Unless you are already a market leader, copyright violation is largely equ…
The Coast Guard is your ally, along with the Navy. Talk to your insurance company; they have lots of experience (or else you picked the wrong one.) Oh, are you equating copyright violation with major theft, murder and associated felonies so heinous that there is actually a separate body of international law to address it? Please don't do that. Unless you are already a market leader, copyright violation is largely equ…
Old methods (90s): - turn to the law (DCMA) - prevent people from modifying code New methods: - change to a SaaS model - change the backend to an API, users order API key - ping home from your software code or every keystroke like in Windows. - free product, offer training + ads
change the backend to an API