Quote:
Originally Posted by gm9
I guess the answer is yes to all. 
And some thoughts on the password question: I'm actually a bit paranoid computer security wise (having some history myself of getting into other people's systems for fun when I was younger, so I know how easy it is) and my systems are certainly better secured than most. However, I never really understood why storing the eq2 login data makes many so nervous. Yes it is the user's decision, but in any case if someone can locally or remotely access the user's computer to read the EQ2 password that user has far bigger problems anyway. It's not like in that situation he could not as easily get rooted or at least have a keylogger installed. Many people probably have their eq2 login stored in their browser anyway for easy forum access - far more likely to get it into wrong hands like that than by writing it into some XML on your harddrive. And again, just by providing that option you are not forcing anybody to use it. Just my 2c... |
LOL, I don't know one person that dabbles in programing that hasn't done shady things or thought about it when they where young and starting out. Except for me *looks over shoulder*
My main concern with maintaining peoples EQ2 Account UN/PW was; I didn't want them coming back to me, saying I jacked that crap, or EQ2 Companion was just a account sniffer etc, etc ... Just look at the post about EQ2MAP and the claims people make about it on OForms.
The good news is, I am putting in the ability to supply username and password. Now that EQ2 can handle attribute white space I can add multi lines scripts to data Objets.