id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
432	writing down filecaps: revise URI scheme	warner		"I'd like to sit down and draw up a plan for ""cap reification"": what are the exact strings used to represent our various file/directory capabilities. We know that there will be at least two kinds (human-readable and packed machine-readable), and that we might want the human-readable ones to be browser-friendly (or 72-column friendly, or concise, or some combination thereof). And we've drawn up a couple of proposals based upon adequate crypto key sizes and ""base62"" encoding schemes, but we haven't finished the roadmap yet.

Various features and tradeoffs:
 * printable
 * pronounceable, error-resistant (base32 with o/0 tolerance)
 * short
 * browser-friendly (starts with {{{http://localhost}}})
 * IANA-friendly (starts with {{{x-tahoe:}}} or {{{tahoe:}}})
 * email friendly (printable and shorter than 72 characters)
 * self-identifying (includes some redundant prefix, version number)
 * visually distinct
"	task	new	major		code-encoding	1.0.0		newcaps newurls