Ivan Shmakov wrote:
Miles Fidelman <[email protected]> writes:
  > Of course one thing to keep in mind about URIs for DHTs is that they
  > really are somewhat meaningless, or at least don't function the way
  > normal URIs do.

  > A URI into a DHT is really for local consumption only - it's a key
  > into the local code that executes the DHT's algorithm, rather than an
  > identifier that can be used across the net.

        I don't quite understand what is meant by “[a] URI into a DHT”,
        but the URN's I'm interested in are perfectly suitable for
        communication, be it in writing, e-mail, or World Wide Web.

        For instance, if you're interested in bits signed by me in
        GNUnet, check [1].

[1] 
gnunet://fs/sks/TU6GGH9COPQLPQTG919BB0QVEVIO1SF1IRGI7ACBGOHKVPNCGRUQG98H4DTTPDNDVMV83E8SI51GR66AL6S47BLLK4LULR8J1A7T188/ivan

What I mean is that

gnunet://fs/sks/TU6GGH9COPQLPQTG919BB0QVEVIO1SF1IRGI7ACBGOHKVPNCGRUQG98H4DTTPDNDVMV83E8SI51GR66AL6S47BLLK4LULR8J1A7T188/ivan

requires that you have the gnunet software installed, and generally you are typing that URL into the gnunet software. It's not like there's a gnunet protocol and API that is generally accessible across the net. This is simply a representation of a gnunet DHT key.



--
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra

_______________________________________________
p2p-hackers mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/p2p-hackers

Reply via email to