The most existential question in crypto: what will be the relationship between tokens and communities?
At stake: can DAOs bring virtue back to scaled organization? Or will they accelerate the economics-only mentalities that have been corroding society?
A way-too-long-๐งต๐
I kinda feel for employees protesting mouse-tracking by Meta.
But also...you worked on behalf of Meta, the pinnacle of surveillance capitalism. What did you think, Facebook would be fine screwing over users for two decades but protect employees?
Companies that figure out which intelligence is theirs will ship mind-blowing software at mind-blowing speed to market it.
Companies that don't may find themselves waiting in fear of each new Anthropic release.
Full piece: https://t.co/Q0g7sXeuWT
Spinning on @andrewhill_'s point that software is the new marketing.
And if software is the new marketing, what's the product?
In most cases, some form of Intelligence. ๐งต
Intelligence in the network.
There's real value in coordinating across actors.
@jaminball 's framing on sources of truth captures this: "The more we automate, the more important it becomes that someone has done the unglamorous work of deciding what the correct answer is."
At root these are databases with software and governance on top, and the ability to extract for the software is eroding rapidly. Trust & the governance layer will provide some stickyness - especially in domains that cross organizations - but maintaining margins will be difficult.
i think it'll be cracked-ish pretty soon, we have a proto-one internally and seeing a bunch of others emerge.
What do you see as the defensibility of this? It's almost all software AI's can build, and state is pretty portable. No doubt where things are going, but not clear to me what the moat is.
An underrated part of chat based AI: the environment is an active contributor.
Traditionally product surfaces facilitated the right user action and collaboration. The best ones got you fast to the right info, feeling, and actions. Maybe some nudges.
Future UIs will be alive, combining both. They should contribute to the conversation and work, not just through text but by adapting the info and layout to the user and collaboration.
I spent 100 hours over the past week researching, writing and editing the piece we just put out.
Itโs a scenario, not a prediction like most of our work. But it was rigorously constructed, dismissing it outright requires the kind of intellectual laziness that tends to get expensive.
And weโve released it for free. Hopefully you enjoy it.
https://t.co/YK8E11GcDU
This is a good example of how development will continue but change domains and abstractions.
Building for agents with tools and context is harder than building for humans with 2d frontends. Agents will do the building, but not everyone will be equally good at vibe guiding them
MCP Servers Are Coming to the Web. MCP lets AI agents call tools on backends. WebMCP brings the same idea to the frontend, letting developers expose their website's functionality as structured tools using plain JavaScript (or even HTML), no separate server needed.
Instead of agents clicking through your UI, they call well-defined tools you control. A W3C proposal from Microsoft and Google, and Chrome 146 already ships an early preview behind a flag.
## How will it work?
WebMCP introduces a `navigator.modelContext` API with two approaches:
- Imperative API: Register tools directly in JavaScript with schemas and callbacks:
```js
navigator.modelContext.registerTool({
name: "add-to-cart",
description: "Add a product to the shopping cart",
inputSchema: {
type: "object",
properties: {
productId: { type: "string", description: "The product ID" },
quantity: { type: "number", description: "Number of items" }
},
required: ["productId"]
},
execute({ productId, quantity }) {
addToCart(productId, quantity);
return { content: [{ type: "text", text: "Item added!" }] };
}
});
```
- Declarative API: Let developers define tools directly in HTML using form attributes, no JavaScript required:
```html
<form action="/todos" method="post"
tool-name="add-todo"
tool-description="Add a new todo item to the list">
<input type="text" name="description" required
tool-prop-description="The text of the todo item">
<button type="submit">Add Todo</button>
</form>
```
This declarative approach is still under active discussion, with the goal of making WebMCP accessible to content creators without JS experience.