3-DArena opened this issue on Apr 25, 2001 ยท 39 posts
whoopdat posted Thu, 26 April 2001 at 1:12 AM
"The purchaser should have some sort of unique identifier that is traceable or verifiable somehow...." That almost sounds something like installing a little "spy" program that sends its information (however limited to Poser) out to a central server, and I know that won't go over well with people based on what I've read. Many people have already expressed how wary they are of having any sort of identifier on their computer since they are seeing it as a security risk for their own system. Whether that's a legitimate argument or not, based on what I've read, it's not practical if you don't want to anger/worry/upset the end user. I think the point I've been worrying about and trying to find out is that regardless of what they do for protection, it will be broken. The best coders out there are hackers and crackers, and well, that's frightening. CL has all right to enjoy sales from their program and should not have to worry about their programs being mass distributed, but again, reality has to step in at some point. This system will not stop piracy, it might delay it a bit, but the end user who bought it is going to have to deal with potential (I think that's a key word here, potential) problems with this security. Some may get it and never have a problem with it, while those of us who replace hardware (hard drives in this case, especially crashed ones or newer and bigger ones), are going to have to deal with talking with someone to be allowed to install a product we own. That's inconvenient. Someone used an analogy of a bank account and all of the trouble of identifying yourself for it, and while that's a fine argument, it's not realistic. When a person sits down in front of a computer, by my experience, they have different expectations. And those expectations right now don't allow for security measures that make things difficult for them when they're used to things going smoothly and easily. When they have to go through new processes, especially those that aren't computer savy, they get upset right quick. New features are great, but new hoops are not. Again, I may be entirely wrong here, and I hope I am, but I see this stuff all of the time. I work with people, and the majority do NOT like it when things chang, and are apt to express it in no uncertain terms.