47 |
Past: |
Past: |
48 |
----- |
----- |
49 |
|
|
50 |
|
2003-07-07 [8.5h, 15.45-16.45, 19.00-20.00, 20.45-23.00, 23.45-4.00]: |
51 |
|
|
52 |
|
- think about Storm pointers. the hairy issue is how to define |
53 |
|
who can sign a pointer block for a given pointer: if you lose |
54 |
|
your key or it gets exposed publically, there must be a |
55 |
|
'social' way to get a new key assigned, so that you can |
56 |
|
change your old pointers. Extremely hairy. |
57 |
|
- Come up with a scheme that *could* just work. Have to write |
58 |
|
a dart this week-- definitely not ready for pegging. |
59 |
|
The surprising thing is that published pointers may have |
60 |
|
to have hierarchical names after all-- urn:blah:foo:bar:baz-- |
61 |
|
because we need some 'social' way to change keys, and there |
62 |
|
probably needs to be a hierarchy of delegation of this right. |
63 |
|
|
64 |
|
Heh, of course if you don't like hierarchical names you could |
65 |
|
simply use the *hash* of such a name as the public identifier |
66 |
|
for your document ;-) |
67 |
|
- mail |
68 |
|
|
69 |
2003-07-06 [7h, 14.30-16.00, 16.15-17.45, 18.45-19.45, 20.00-22.30, 2.00-3.30]: |
2003-07-06 [7h, 14.30-16.00, 16.15-17.45, 18.45-19.45, 20.00-22.30, 2.00-3.30]: |
70 |
|
|
71 |
- mail |
- mail |