![]() |
|
|
|
#1
|
|||
|
|||
|
[ QUOTE ]
I started out with a registration system that didn't connect to the internet. After months of dealing with dozens of daily emails saying "I need a new code", I implemented the current system. [/ QUOTE ] I have absolutely no objection to PAHUD connecting once for registration - it is the ongoing connections that I have an issue with. I can understand your concern with pirating, but I don't see why I have to take a (minor) risk to protect your business when any competent software hacker will find a way round this protection anyway. As I have a use for the product I'll have to put up with it, but don't pretend that it isn't an issue. |
|
#2
|
|||
|
|||
|
The primary use of the registration system isn't really to reduce piracy. It's to prevent accidental and deliberate abuse of purchased licenses. The registration system is to allow my customers the flexibility of upgrading/formatting their computers without having to worry about asking for a new code. The software must connect every few days in order to determine if other computers have used the code. A one time registration connection would be useless for this application.
|
|
#3
|
|||
|
|||
|
[ QUOTE ]
The primary use of the registration system isn't really to reduce piracy. It's to prevent accidental and deliberate abuse of purchased licenses. [/ QUOTE ] yea, I though so. It's like the microsoft's on-line registration. The primary target are "friends" of someone who bought one single licence and want to share it. But it's good you try to find another solution for those who don't like progs communication with random servers (though they are somewhat trustworthy). |
![]() |
| Thread Tools | |
| Display Modes | |
|
|