Re: Namespaces (was: new.net: yet another dns namespace overlay play)
Joshua Goodall <joshua@roughtrade.net> writes: [ ... ]
A better method for addressing data would be based on source-brokered, signed, distributed caches of keywords that can be search and, more importantly, bookmarked in the context of each signer.
I'm not sure I want something that elaborate to ftp a file from my laptop to my desktop. And I certainly don't want to have to remember IP addresses for both of them. I think DNS works pretty well. You just have to think of it like an 800 number --- 800 numbers are ambiguous (1-800-CONTACTS could provide information about how to contact people, information about aliens contacting the earth, or information about the old PBS show 3-2-1 Contact!, but it in fact sells contact lenses), but they're still easier to remember than the digits. ------ScottG.
Interesting analogy...How many here are old enough to remember when (in the US) the first two digits of the exchange meant something? 617-GArden8-xxxx was the houses in/around the garden section of town long ago & far away... But we've drifted well off operational topic. Scott Gifford wrote:
Joshua Goodall <joshua@roughtrade.net> writes:
[ ... ]
A better method for addressing data would be based on source-brokered, signed, distributed caches of keywords that can be search and, more importantly, bookmarked in the context of each signer.
I'm not sure I want something that elaborate to ftp a file from my laptop to my desktop. And I certainly don't want to have to remember IP addresses for both of them.
I think DNS works pretty well. You just have to think of it like an 800 number --- 800 numbers are ambiguous (1-800-CONTACTS could provide information about how to contact people, information about aliens contacting the earth, or information about the old PBS show 3-2-1 Contact!, but it in fact sells contact lenses), but they're still easier to remember than the digits.
------ScottG.
participants (2)
-
bob bownes -
Scott Gifford