We should aim for a user-first model.

· Bits and Bobs 5/6/24

Not origin first.

That prioritizes the domain, and the ease of implementation.

It leads to accelerated hyper-aggregation.

Not local first.

An improvement over origin-first, but not enough.

It still by default prioritizes the domain by default.

The combinatorial possibility of software is still not possible by default.

Instead: User-first.

Operating on the user's turf under their full control.

This can be local… or, with confidential compute, remote.

Not sharded by domain; one file system for experiences to coordinate in.

More challenging to implement, but unlocks a universe of combinatorial potential.