Base32 ID encoding option

Garret -

I've been thinking about id URL encoding. What do you think about 5
additional variables, corresponding to the current ones, for Base32
encodings of the ID? Like bd, b1, ... b4 or whatever? Base32 is more or
less guaranteed to be compatible and collision-less on every filesystem
and would seem to eliminate those problems. Encoders that use
string IDs could still have the option of using the strings directly.

Or if "seeing" the ID in the filenames isn't a requirement, I suppose we
could alternatively just switch to Base32 entirely, as it's more compact
than hex and spreads the files out among more, but still not an
overwhelming number, of directories.

Skef