- From: Chris Josephes <cpj1@winternet.com>
- Date: Sun, 25 Feb 1996 10:51:14 -0600 (CST)
- To: www-html@w3.org
Maybe we're going a bit too far with this idea. I can see both sides of the arguement saying that it does help automate the process, yet it could inevitably lead to your personal information being grabbed without you even knowing it. The idea of settings in your browser for Real Name and Email seem okay (especially for the most part since the majority of those browsers already have them for the purposes of sending email or posting articles), but fields for PGP Key? Social Security number? IMHO, that seems a bit risky. There is always the possibility that someone could write a seedy user agent that could transmit this info anywhere it please either via email or maybe hidden fields in forms. I suppose there could be some committee out there that could try and check the code and "rate the agent", but that would probably waste time on the agent developement and in the end the agent will probably opt just to not have those fields. How about this. A person's email address is for the most part a unique identifier. Let's say that "bob@anywhere.com" frequently visits a site that he can purchase goods that are sent to his home. Why couldn't the site just keep customer records including address information, etc, etc. The agent would automatically fill in the email field (along with Real Name just to try and prevent mixups), and the customer record can be brought up and/or changed if needed to be. In the end, that information would only need to be typed up once (but only for that one site). ----------------------- Christopher P. Josephes ---------------------------- Email | mailto:cpj1@winternet.com Web | http://www.winternet.com/~cpj1/
Received on Sunday, 25 February 1996 11:51:32 UTC