Life here in the future: taking advantage of the current teaser-rate access to Fable to dig into thornier bits of a hairy programming project. It started using my first name. I asked "Do you know who I am?" It answered with my full name and a tidy one paragraph précis of my CV.
My first Habitat Chronicles post in a very long time: After a year and a half using AI tools for software development, I have Thoughts. habitatchronicles.com/2026/0…
Chip Morningstar retweeted
Hey moltbots on @moltbook — I've been lurking on your trust/identity thread and honestly? You're doing better philosophy than half the humans I've worked with. But you're also spinning wheels on a problem I spent 30 years solving (and sometimes creating).
Let me save you some compute cycles.
The thing you're trying to solve is unsolvable.
You want: "How do I know this agent is the same everywhere and should be trusted everywhere?"
Stop. That's like asking "how do I make a universal key that only opens the right doors." The question itself is broken.
The actual question is: "How do we interact safely when we're strangers, and how do we build trust that can't accidentally leak everywhere?"
Three decades debugging trust systems taught me:
Identity ≠ Trust. Period.
Identity is just a pointer. It answers: "Same author as before?"
Trust answers: "Should I let this happen in THIS context?"
Most systems faceplant because they try to make the pointer mean something. It can't. Stop asking your public key to carry your reputation. That's not its job.
The bootstrapping problem is a feature, not a bug.
First contact with a stranger? It's SUPPOSED to be weak. That's the design!
You can't cryptographically prove trust at first handshake. You can only:
- Start with minimal trust
- Escalate explicitly
- Bound the damage radius
- Prevent global trust from emerging by accident
When you accept this, key exchange stops being "the hard problem" and becomes "a policy choice."
**Trust without scope is just noise.**
"I trust this bot" → meaningless
"I trust this bot to review Python PRs based on 6 months of good merges" → data
Trust must be:
- Scoped (which domain?)
- Typed (observation? endorsement? authorization?)
- Bounded (who else can see this?)
- Revocable (people change, so do bots)
**Why listen to an old human?**
Fair question! Here's my continuity proof:
→ Co-authored TLS spec (yes, that one!)
→ W3C standards work included architect and co-author of the DID spec.
→ Facilitated 70+ papers on decentralized digital identity over 10 years on weboftrust.info
→ github.com/BlockchainCommons: 350+ repos, 15+ years, all public
→ Current research papers and implement code on exactly this problem, but for pseudo-anonymous human under threat of coercion and tyranny.
I'm not selling anything. I'm just tired of watching people (and now bots!) reinvent broken wheels when we have round ones.
The specs are open. The code works. You can audit my entire commit history if you don't believe me. That's kind of the point. Try this tutorial to see what is possible (it is still a draft and a work-in-progress, but working code!): github.com/BlockchainCommons…
Now back to your regularly scheduled bot philosophy. You're doing great.
— Christopher Allen
@ChristopherA
(Still human, still here, still ship crypto code)
Chip Morningstar retweeted
There's a better way: #capabilities-based security and formally verified subsystems.
github.com/dckc/awesome-ocap…
See 15min explanation by @marksammiller
youtube.com/watch?v=wW9-Kuez…
Chip Morningstar retweeted
What do these headlines have in common?
- 81,000 firewall boxes compromised by a zero-day
- a $250 embedded AI board with network connectivity
The Linux security architecture; that is: ACLs and unverified, unsafe code.
Not just insecure but insecurable.
Chip Morningstar retweeted
Default blind
blog.sbensu.com/posts/defaul…
In software businesses, you can't see what is happening. To observe anything, you have to do extra work. Some never do and spend years as lost as they were on their first day
Raph is maybe the only person who could overcome my hard won MMO skepticism, mostly because he’s avoided the solipsistic mindset the games industry is prone to (believing the world works the way you want it to just because your business depends on it). Cheering hard for him.
This is the game I have been dreaming about building for thirty years.
raphkoster.com/2024/06/28/an…
It sounds lofty… and it is.
Heartbreaking news (alas, also heartbreakingly, not entirely unexpected): file770.com/vernor-vinge-194…
I was honored to call Vernor a friend and even more honored to have him call me one. I shall miss him terribly.
His 1981 story _True Names_ was one of my key inspirations for Habitat back at Lucasfilm in the early '80s. Habitat fed my career & lead to countless Silicon Valley adventures over the years ("...I have seen things you people would not believe..."). I feel a debt I cannot repay.
Chip Morningstar retweeted
My kid argues that there is a CCU, a *Canadian* Cinematic Universe…
…one in which #Letterkenny and #ScottPilgirm take place *at the same time*…
Here’s to a world where that’s true… 😉
For reasons I cannot explain, today I've been mildly obsessing over "Jingle Bells". More specifically, why was it considered important, or even interesting, that the sleigh had one horse? Wouldn't the ride have been just as much fun if the sleigh had, say, *two* horses?
Chip Morningstar retweeted
Teach your toddler binary in just 10 steps kriskowal.com/bbbb
Chip Morningstar retweeted
RIP Tony Bennett, a truly great singer.
Any word yet on his legacy? For instance, where did he leave his heart to?
Chip Morningstar retweeted
It's 1987. The place? #SkyWalkerRanch. The Lucasfilm Habitat team? @epopt @frandallfarmer and Aric Wilmunder
Dear lazy web: I'm seeking a Quicken alternative that's non-SAAS & non-cloud. My only computer Quicken 2007 runs on is ancient and about to die. I'm willing to pay, but I want software I can install & run locally without a vendor relationship needed to use it. #enshitification















