1994-07-16 - Re: Card Playing Protocol

Header Data

From: tcmay@netcom.com (Timothy C. May)
To: kentborg@world.std.com (Kent Borg)
Message Hash: 21d60db6dff6c3ceb93de1b573d7c69b365d7836885e44dce390341fe8346aca
Message ID: <199407161737.KAA26905@netcom2.netcom.com>
Reply To: <199407160808.AA09114@world.std.com>
UTC Datetime: 1994-07-16 17:37:43 UTC
Raw Date: Sat, 16 Jul 94 10:37:43 PDT

Raw message

From: tcmay@netcom.com (Timothy C. May)
Date: Sat, 16 Jul 94 10:37:43 PDT
To: kentborg@world.std.com (Kent Borg)
Subject: Re: Card Playing Protocol
In-Reply-To: <199407160808.AA09114@world.std.com>
Message-ID: <199407161737.KAA26905@netcom2.netcom.com>
MIME-Version: 1.0
Content-Type: text/plain



Kent Borg writes:

> Tim says (roughly): "Go for it, too bad you are doomed to lose
> interest shortly."
>  
> Geeze, I hate people who make generalizations which are, well, likely
> to be borne out yet one more time.  (I *hate* that!)

No, I think it's a fine project, certainly more useful in the long run
than another PGP shell. But also more complicated, if done right.
(Done right = reusable building blocks for the various needed primitives.)

> So I am either supposed to put my tail between my legs now, or take
> this as a challenge to "Follow through this time.", or let it soon die
> quietly and hope Tim takes mercy and doesn't rub my nose in it.
>  
> Grrr.  I *hate* reality.

Glad you are taking my comments in the spirit in which they were
given. There are some pretty good reasons many of the ideas excitedly
discussed here never reach fruition:

1. No time. Most people have full-time jobs doing other things.

2. No funding sources to _force_ people to complete things they've
already been paid for.

3. No group of co-workers to chat with, to reignite interest, to exert
peer pressure to finish. It's just _so easy_ to let a project kind of
s-l-i-d-e  a-w-a-y...


> So here is where I am:
>  
> 1) I am wondering whether a "digital deck of cards" is a good choice.

Read up on the "playing cards by telephone" papers of the early to
mid-80s. Maybe implementing just one of the sets of ideas would give
your further insights.

> 2) If it is, I am wondering how the protocol would roughly be framed
>    (Fundamental card operations, etc.), with an eye towards what the
>    cryptographic protocols can offer.

That's the central issue. 

> 3) Then, if things make sense, appear tractable, and (drum roll) I
>    haven't gone onto fresher blue-sky ideas, I figure out how to start
>    building the damn thing.
>  
> 4) And if I ever get to building it I will start first with the little
>    pieces (the cryptographic fragments) which might be useful
>    individually when I lose interest in building the larger beast.
>  
> I assume that I will have to do real work at each of these
> stages--though I welcome any help.  Both now when the talk is still
> cheap and later when the bits hit the disk.

Lots of work. Remember, the mathematicians and computer people who did
these papers did not bother to build them into computer code, though
some of them surely could have if it were easy. (Chaum's people built
a running simulation--and crypto simulation is what we're talking
about here--of digital cash, but the version I saw was unusable by
other programs. That is, it was a "user at the console" sort of thing,
not a tool or class library or even a function call.)

What's lacking in crypto is a reasonable "framework" for these
concepts and functions to live it.


> As for getting people to want to use this digital deck of cards, I
> rely on my passion for good user interface design combined with the
> continuing popularity of card games.  (And people's continued interest
> in playing games with other people rather than just computers.)

Good user interface is probably the wrong thing to be thinking about
now, if the goal is wide use. Think "client-server" (or choose your
own paradigm). The building blocks are more important than a snazzy
Windows or Mac interface.

> So I am currently at step #.  Is the Card Playing Protocol a good
> choice for being:
>  
> 1) cryptographically interesting

Yes,

> 2) tractable

Unknown.

> 3) "harmless"

Not a real issue.

> 4) appealing to users?

For researchers, it would be interesting to have the set of
abstractions reified into running code. This is a longstanding
interest of many of us, and was one of the motivations two years ago
to form the Cypherpunks group. Eric and I figured it was high time to
take the various theoretical abstractions and implement them in code;
we hoped that a bunch of people would generate "Pretty Good Digital
Money," "Pretty Good DC-Nets," etc. So far, it's been slow. (And some
actual deployments, such as Digital Money, have faltered for other
reasons. Kent should look at MM and why it isn't in wider use and try
to learn some lessons for a gambling scheme.)

> Comments?  (You too Tim.)

See above.

--Tim May


-- 
..........................................................................
Timothy C. May         | Crypto Anarchy: encryption, digital money,  
tcmay@netcom.com       | anonymous networks, digital pseudonyms, zero
408-688-5409           | knowledge, reputations, information markets, 
W.A.S.T.E.: Aptos, CA  | black markets, collapse of governments.
Higher Power: 2^859433 | Public Key: PGP and MailSafe available.
"National borders are just speed bumps on the information superhighway."




Thread