[Gzz-commits] journals benja

[Benja Fallenstein]

CVSROOT:        /cvsroot/fenfire
Module name:    journals
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/07/07 21:50:51

Modified files:
        .              : benja 

Log message:
        Another day of thinking about Storm, but finally
        with results-- need to write dart and get back to ff work.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/journals/benja.diff?tr1=1.77&tr2=1.78&r1=text&r2=text

Patches:
Index: journals/benja
diff -u journals/benja:1.77 journals/benja:1.78
--- journals/benja:1.77 Sun Jul  6 21:47:14 2003
+++ journals/benja      Mon Jul  7 21:50:51 2003
@@ -47,6 +47,25 @@
 Past:
 -----
 
+2003-07-07 [8.5h, 15.45-16.45, 19.00-20.00, 20.45-23.00, 23.45-4.00]:
+
+- think about Storm pointers. the hairy issue is how to define
+  who can sign a pointer block for a given pointer: if you lose
+  your key or it gets exposed publically, there must be a
+  'social' way to get a new key assigned, so that you can
+  change your old pointers. Extremely hairy.
+- Come up with a scheme that *could* just work. Have to write
+  a dart this week-- definitely not ready for pegging.
+  The surprising thing is that published pointers may have
+  to have hierarchical names after all-- urn:blah:foo:bar:baz--
+  because we need some 'social' way to change keys, and there
+  probably needs to be a hierarchy of delegation of this right.
+
+  Heh, of course if you don't like hierarchical names you could
+  simply use the *hash* of such a name as the public identifier
+  for your document ;-)
+- mail
+
 2003-07-06 [7h, 14.30-16.00, 16.15-17.45, 18.45-19.45, 20.00-22.30, 2.00-3.30]:
 
 - mail