|Think about Loose Coupling|
Disclaimer: I am posting this as a reply because I am apparently being ignored by jcwren, so don't downvote me for posting something that should have been sent as a /msg.
For starters, I did not mean to sound like I am bashing the program (XPFixation). I think a lot of the tools available on the site concerning PerlMonks are really hip and cool, including XPFixation.
Also, it's not like I am scared that some monk is going to write a program to snoop the registry values and send them via e-mail or anything... and even if someone did, I only use my PerlMonks password for PerlMonks, so the most damage they could do is login and yell at people in the chatterbox, resulting in a series of downvotes. (Ack! Please, nobody think of this!)
And even though I actually stated it was for 'security' reasons, I think it is really just for an additional feature to the program... how many programs store 'sensitive' information in plain text? It would be great to see some kind of protection (even if it is mild) added to the program.
So I apologize if I sounded rude or against all of the work you put into XPFixation! It was programmed in C, so I can't really comment on the programming (as I lack the skills of the C language). Besides, knowing that I am losing XP all of the time is helpful. ;)
In reply to Re: (jcwren) XPFixation -- One Security 'feature'