Philosophy Mondays: Human-AI Collaboration
Today's Philosophy Monday is an important interlude. I want to reveal that I have not been writing the posts in this series entirely by myself. Instead I have been working with Claude, not just for the graphic illustrations, but also for the text. My method has been to write a rough draft and then ask Claude for improvement suggestions. I will expand this collaboration to other intelligences going forward, including open source models such as Llama and DeepSeek. I will also explore other moda...

Intent-based Collaboration Environments
AI Native IDEs for Code, Engineering, Science
Web3/Crypto: Why Bother?
One thing that keeps surprising me is how quite a few people see absolutely nothing redeeming in web3 (née crypto). Maybe this is their genuine belief. Maybe it is a reaction to the extreme boosterism of some proponents who present web3 as bringing about a libertarian nirvana. From early on I have tried to provide a more rounded perspective, pointing to both the good and the bad that can come from it as in my talks at the Blockstack Summits. Today, however, I want to attempt to provide a coge...
Share Dialog
So given the previous parts of this series (1, 2, 3), what might an alternative solution to the global namespace for people look like? First, we should have some criteria for how the system operates. Here are the ones that come to mind:
Secure decentralized operation that’s not controlled by a single entity
Human readable/memorable names
Globally unique
Until yesterday I was blissfully unaware that there has been a bunch of work on this starting with an assertion by Zooko (talk about a unique name) that you can’t actually have all three in a naming system, followed by a post from yesterday (!) by Aaron Swartz proposing a solution (thanks to e.p.c. for pointing me to this). I have read Aaron’s post a couple of times but that’s only made me realize how much crypto background I lack to judge its merit. So rather than spend more time on that let me flush out a bit of an alternative model.
We are a bit shy of 7 billion people in the world. Apparently, the U.S. Census Bureau statistics suggest that there are about
So given the previous parts of this series (1, 2, 3), what might an alternative solution to the global namespace for people look like? First, we should have some criteria for how the system operates. Here are the ones that come to mind:
Secure decentralized operation that’s not controlled by a single entity
Human readable/memorable names
Globally unique
Until yesterday I was blissfully unaware that there has been a bunch of work on this starting with an assertion by Zooko (talk about a unique name) that you can’t actually have all three in a naming system, followed by a post from yesterday (!) by Aaron Swartz proposing a solution (thanks to e.p.c. for pointing me to this). I have read Aaron’s post a couple of times but that’s only made me realize how much crypto background I lack to judge its merit. So rather than spend more time on that let me flush out a bit of an alternative model.
We are a bit shy of 7 billion people in the world. Apparently, the U.S. Census Bureau statistics suggest that there are about
Philosophy Mondays: Human-AI Collaboration
Today's Philosophy Monday is an important interlude. I want to reveal that I have not been writing the posts in this series entirely by myself. Instead I have been working with Claude, not just for the graphic illustrations, but also for the text. My method has been to write a rough draft and then ask Claude for improvement suggestions. I will expand this collaboration to other intelligences going forward, including open source models such as Llama and DeepSeek. I will also explore other moda...

Intent-based Collaboration Environments
AI Native IDEs for Code, Engineering, Science
Web3/Crypto: Why Bother?
One thing that keeps surprising me is how quite a few people see absolutely nothing redeeming in web3 (née crypto). Maybe this is their genuine belief. Maybe it is a reaction to the extreme boosterism of some proponents who present web3 as bringing about a libertarian nirvana. From early on I have tried to provide a more rounded perspective, pointing to both the good and the bad that can come from it as in my talks at the Blockstack Summits. Today, however, I want to attempt to provide a coge...
Share Dialog
Subscribe to Continuations
>500 subscribers
Subscribe to Continuations
>500 subscribers
Each record in the GPN would consist of at least the following (UserID, username, authprovider, authprotocol). The latter two would be how people actually use their usernames when signing up for a service – generally this will initially be the registrar itself but the user should be able to move that to other providers. You simply enter your globally unique username and hit a generic “Register” button, which using your record in the GPN can figure out where to send you to authenticate.
I think one reasonable objection to all of this would be that it is simply too late. The cat’s out of the bag. People already have usernames on tons of services. But I don’t think we should give up, at least not yet (apparently Jeff Atwood thinks so also). If a system such as this came into being in the next couple of years and was launched with some of the currently biggest username providers as initial registrars, then many people could get exactly the username they already have on these (and many other services). That would allow the existing namespaces to be converged with the GPN. What would be needed for all of this is someone like ICANN (ICANN itself?) to figure out a scheme for how UserIDs get partitioned across registrars and what database mechanism to use to for assuring global uniqueness of usernames. The model for the database itself should most likely be DNS (someone with more in depth knowledge of DNS might be able to tell whether DNS itself could be used as it is today).
I would love to hear from folks whether they think this is completely crazy in being undesirable (e.g., because not entirely distributed), not technically feasible, not politically/commercially accomplishable, etc.
P.S. Since people are likely to bring it up: webfinger may be a much more pragmatic way to get to a similar place in the end. It does, however, give up on a single global namespace for people that is separate from the domain name system (and with that the most likely give us up on individuals truly controlling their usernames).

Each record in the GPN would consist of at least the following (UserID, username, authprovider, authprotocol). The latter two would be how people actually use their usernames when signing up for a service – generally this will initially be the registrar itself but the user should be able to move that to other providers. You simply enter your globally unique username and hit a generic “Register” button, which using your record in the GPN can figure out where to send you to authenticate.
I think one reasonable objection to all of this would be that it is simply too late. The cat’s out of the bag. People already have usernames on tons of services. But I don’t think we should give up, at least not yet (apparently Jeff Atwood thinks so also). If a system such as this came into being in the next couple of years and was launched with some of the currently biggest username providers as initial registrars, then many people could get exactly the username they already have on these (and many other services). That would allow the existing namespaces to be converged with the GPN. What would be needed for all of this is someone like ICANN (ICANN itself?) to figure out a scheme for how UserIDs get partitioned across registrars and what database mechanism to use to for assuring global uniqueness of usernames. The model for the database itself should most likely be DNS (someone with more in depth knowledge of DNS might be able to tell whether DNS itself could be used as it is today).
I would love to hear from folks whether they think this is completely crazy in being undesirable (e.g., because not entirely distributed), not technically feasible, not politically/commercially accomplishable, etc.
P.S. Since people are likely to bring it up: webfinger may be a much more pragmatic way to get to a similar place in the end. It does, however, give up on a single global namespace for people that is separate from the domain name system (and with that the most likely give us up on individuals truly controlling their usernames).

No activity yet