Skip to Content.
Sympa Menu

bluesky - Re: Naming via SDSI

bluesky AT lists.ibiblio.org

Subject: Global-Scale Distributed Storage Systems

List archive

Chronological Thread  
  • From: Brandon <blanu AT uts.cc.utexas.edu>
  • To: Global-Scale Distributed Storage Systems <bluesky AT franklin.oit.unc.edu>
  • Subject: Re: Naming via SDSI
  • Date: Wed, 7 Mar 2001 02:51:36 -0600 (CST)



> http://www.cnn.com/2001/TECH/space/03/06/mir.fungus.reut/index.html
>
> Given this primitive level of automation, which is already necessary
> for links to be passed around at all, a link with a 160 bit unforgeable
> number can look like d787ef5c05460da6cf3d6aa1633655d8861e20f1 in hex or
> like 14fvXAVGDabPPWqhYzZV2IYeIPE in a base-64 encoding, which is easy to
> cut and paste; easier in fact than modern URLs which often span more than
> one line and get forcibly line-wrapped by brain-damaged email software.

The URL is still easier to communicate by voice than then hex or
base-64. I think that the importance of a voice-friendly encoding is often
overlooked because people underestimate the amount of URL information
communicate over the phone and in person. Of course, I don't have any
particular ideas on how to convert 160-bit hashes into more voice-friendly
encodings, but the least you could do is use hex instead of base-64.






Archive powered by MHonArc 2.6.24.

Top of Page