I've been reading through the codebase and the architecture already has all the pieces of a personal computer: a persistent Ed25519 identity, iroh's QUIC transport, a blob store, a local SQLite database, and a task runtime with structured shutdown. What it doesn't have yet is an application model that lets arbitrary programs plug into those primitives.
The idea is to promote the iroh node to a kernel, and demote social to one app running on top of it.
The comparison I keep reaching for is Urbit. The same ambition of a personal network-attached computer with a stable identity, but built on modern primitives (Rust, iroh, QUIC) instead of a novel VM and an esoteric language.
The social feature set wouldn't change at all; it would just be the first app on a platform rather than being the whole platform.
Curious whether this aligns with where you see this going, or whether there are constraints I'm missing from the codebase.
I've been reading through the codebase and the architecture already has all the pieces of a personal computer: a persistent Ed25519 identity, iroh's QUIC transport, a blob store, a local SQLite database, and a task runtime with structured shutdown. What it doesn't have yet is an application model that lets arbitrary programs plug into those primitives.
The idea is to promote the iroh node to a kernel, and demote social to one app running on top of it.
The comparison I keep reaching for is Urbit. The same ambition of a personal network-attached computer with a stable identity, but built on modern primitives (Rust, iroh, QUIC) instead of a novel VM and an esoteric language.
The social feature set wouldn't change at all; it would just be the first app on a platform rather than being the whole platform.
Curious whether this aligns with where you see this going, or whether there are constraints I'm missing from the codebase.