1997-01-21 - Re: microcurrency: Netscape vs. Microsoft

Header Data

From: Lucky Green <shamrock@netcom.com>
To: “Vladimir Z. Nuri” <vznuri@netcom.com>
Message Hash: 0e368805e1fa7b1cf8521b88cc7fa1fa87594f264db2ae857232f2dc2d5bffef
Message ID: <3.0.32.19970120210810.006dd5cc@192.100.81.126>
Reply To: N/A
UTC Datetime: 1997-01-21 05:12:29 UTC
Raw Date: Mon, 20 Jan 1997 21:12:29 -0800 (PST)

Raw message

From: Lucky Green <shamrock@netcom.com>
Date: Mon, 20 Jan 1997 21:12:29 -0800 (PST)
To: "Vladimir Z. Nuri" <vznuri@netcom.com>
Subject: Re: microcurrency: Netscape vs. Microsoft
Message-ID: <3.0.32.19970120210810.006dd5cc@192.100.81.126>
MIME-Version: 1.0
Content-Type: text/plain


At 11:46 AM 1/20/97 -0800, Vladimir Z. Nuri wrote:
>[microcurrency]
>>It will also not catch on until there are better standards involving
>>microcurrency transactions amongst the vendors.  It would also help if
>>there was a single interface (or "helper app") for whatever vendor you
>>decided to go with.

I am not sure that is feasible. Single interface, perhaps. Sun's Java Wallet is  step in this direction. Single helper app, not a chance. The systems are too different, and do not share a sufficient number of properties, to use the same helper app.

>as I see it, I think there are a few key standards that need 
>to be devised: 
>
>1. an html tag that indicates how much a link costs, probably in
>the <a href="" cost=xx> type syntax

This could be done, but is, IMHO, too inflexible.

>2. modification of http to support a payment mechanism, by sending
>a token.

Take a look at PEP and UPP. This may not be what you are looking for, but it is a start.  Available at any IETF draft repository.
[...]

>>Currently every vendor of payment schemes has made it proprietary in some
>>way.  (At least the ones I have seen.)  This means that if the user visits
>>three different web pages, each using a payment scheme from a different
>>vendor, that user has to be signed up with all of those vendors.  (Or at
>>least have their helper apps.)

The systems are *not* interchangeable due to fundamental differences in the design. This is not a software/UI issue.

I do not expect the signup requirements to last much longer. To give just one example, take a look at the current discussions on dev-lucre, a list for the Unofficial Cypherpunks Implementation of Ecash. [Sorry, I don't have the archive URL.]

http://www.isaac.cs.berkeley.edu/ntlucre/ has the latest version.

The list is currently discussing an ActiveX Ecash control. With -lucre, you no longer need to sign up with an issuer. Assuming an ActiveX control, the client software installs itself. As to the merchant software, Stronghold already ships with Ecash support built in. Netscape has announce that Navigator will ship with CyberCash. There is definitely movement at the browser/server end.





-- Lucky Green <mailto:shamrock@netcom.com> PGP encrypted mail preferred
   Make your mark in the history of mathematics. Use the spare cycles of
   your PC/PPC/UNIX box to help find a new prime.
   http://www.mersenne.org/prime.htm





Thread