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...
Yesterday, I met with someone launching an exchange for privately held companies . The idea is to have a marketplace that is somewhere between the inefficient one-off negotiation of secondary sales on one end and going public on the other. Pretty quickly our discussion turned to the disclosure of information about these private companies. One of the reasons given for being a private is so as to not have to disclose a lot of information to others (including potential competitors). So how do you control the information in such a new marketplace? The proposals generally revolve around having some kind of controlled distribution lists and the ability to “block” some potential recipients. Yet, once you release information to a sizable group, it is a lot more likely that information will wind up with people you were trying to block.
The fundamental structure of this problem is the same we are all grappling with in different guises: the boundary between private and public (in the example above even with those terms). Abstracted, the issue is as follows: we have some information that we (believe) we want to share only with some people and not with others. But with the cost of capturing and distributing information at essentially zero, “redistribution” or “leaking” of this information is becoming widespread. This is the problem of the music industry. It is the problem of disclosing data on a private company, etc.
There have been two divergent responses to this problem. The first is the attempt to impose constraints. These come in may different forms – from controlled distribution lists and approved friends all the way to “trusted” computing and DRM. The effectiveness of such a constraint depends on the cost that it imposes relative to the value of the information. The value of music, computer games, etc. is extremely high and not surprisingly, all the investment in DRM has failed to stop redistribution. But the same logic applies for something as simple as the “looking for” field in Facebook profiles. Most changes to that field are not sufficiently “valuable” for anyone to bother to redistribute, but when Marissa Meyer had hers set to “random play,” a screenshot of it quickly appeared on Valleywag and can still be found on Gawker.
The second response has been to design systems which default to sharing. These include flickr for photos, del.icio.us for bookmarks,
Yesterday, I met with someone launching an exchange for privately held companies . The idea is to have a marketplace that is somewhere between the inefficient one-off negotiation of secondary sales on one end and going public on the other. Pretty quickly our discussion turned to the disclosure of information about these private companies. One of the reasons given for being a private is so as to not have to disclose a lot of information to others (including potential competitors). So how do you control the information in such a new marketplace? The proposals generally revolve around having some kind of controlled distribution lists and the ability to “block” some potential recipients. Yet, once you release information to a sizable group, it is a lot more likely that information will wind up with people you were trying to block.
The fundamental structure of this problem is the same we are all grappling with in different guises: the boundary between private and public (in the example above even with those terms). Abstracted, the issue is as follows: we have some information that we (believe) we want to share only with some people and not with others. But with the cost of capturing and distributing information at essentially zero, “redistribution” or “leaking” of this information is becoming widespread. This is the problem of the music industry. It is the problem of disclosing data on a private company, etc.
There have been two divergent responses to this problem. The first is the attempt to impose constraints. These come in may different forms – from controlled distribution lists and approved friends all the way to “trusted” computing and DRM. The effectiveness of such a constraint depends on the cost that it imposes relative to the value of the information. The value of music, computer games, etc. is extremely high and not surprisingly, all the investment in DRM has failed to stop redistribution. But the same logic applies for something as simple as the “looking for” field in Facebook profiles. Most changes to that field are not sufficiently “valuable” for anyone to bother to redistribute, but when Marissa Meyer had hers set to “random play,” a screenshot of it quickly appeared on Valleywag and can still be found on Gawker.
The second response has been to design systems which default to sharing. These include flickr for photos, del.icio.us for bookmarks,
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...
Subscribe to Continuations
Subscribe to Continuations
>500 subscribers
>500 subscribers
No activity yet