Opened at 2008-02-08T03:29:39Z
Last modified at 2009-11-03T00:33:53Z
#306 new task
Clean up code terminology: "SSK" vs "slot", etc
Reported by: | warner | Owned by: | somebody |
---|---|---|---|
Priority: | minor | Milestone: | undecided |
Component: | code | Version: | 0.7.0 |
Keywords: | mutable newcaps docs | Cc: | |
Launchpad Bug: |
Description
split out from #207:
code terminology: share vs slot vs container, "SSK" vs mutable file vs slot. We need to nail down the meanings of some of these and clean up the code to match. Zooko thinks that the name "SSK" -- "Sub-Space Key" -- is not directly applicable to our mutable file URIs.
Some of these terms are embedded in hash tags, and may be difficult to change. It may be easiest to change them when we switch to DSA keys (#217).
Change History (4)
comment:1 Changed at 2008-04-24T23:44:42Z by warner
- Component changed from code-encoding to code-mutable
comment:2 Changed at 2008-06-01T20:57:31Z by warner
- Milestone changed from eventually to undecided
comment:3 Changed at 2009-10-28T03:30:42Z by davidsarah
- Keywords newcaps added
comment:4 Changed at 2009-11-03T00:33:53Z by davidsarah
- Component changed from code-mutable to code
- Keywords docs added
- Owner set to somebody
- Summary changed from clean up mutable-file code terminology: "SSK" vs "slot", etc to Clean up code terminology: "SSK" vs "slot", etc
The immutable terminology needs clearing up as well. For example, CHKs are not really content-hash-keys: Tahoe uses "CHK" to refer to caps for both convergent and non-convergent immutable files (and directories when #607 is done); also, convergent encryption uses a secret to avoid guessing attacks, which is sufficiently different from Freenet CHKs that it should be called something else.
Tagging issues relevant to new cap protocol design.