Chip Morningstar

[Chip Morningstar @epopt]

@perrymetzger It took a bewildering variety of hardware acquired second hand at ruinous expense, an amazing professional network to draw on, and several years of effort, to produce one (1) transistor that could be said to work if you squinted at various instrument graphs in just the right way.

[Chip Morningstar @epopt]

@perrymetzger I have a friend who did, in fact, build a chip fab in their garage. But they're also extraordinarily smart, competent, and hard working, with a breathtaking range of knowledge across a vast swath of directly relevant subject domains.

[Chip Morningstar @epopt]

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.

[Chip Morningstar @epopt]

@perrymetzger The most important thing you discover when you get rid of a bottleneck is the next bottleneck.

[Chip Morningstar @epopt]

Fable spooks like a nervous horse.

[Chip Morningstar @epopt]

@perrymetzger A lot of people rely on others to tease this out of them via some combination of intuition and interrogation. This ability to discern desire is itself a very valuable skill, which I can imagine AIs soon acquring but which they do not yet have.

[Chip Morningstar @epopt]

@perrymetzger Aside from needing basic communication skills, in order to give effective directions you need to be clear yourself about what you actually want. The ability to attain such clarity is itself a skill, one I think many people just don't have.

[Chip Morningstar @epopt]

@paulg A wise mentor once told me that many investors’ way of saying no is to remain enthusiastic — forever.

[Chip Morningstar @epopt]

@karma_gardener @perrymetzger @jollier_raptor I’d be curious to see the corresponding graph for watering golf courses.

[Chip Morningstar @epopt]

@ryaneshea What does the Y axis on the first graph represent? We understand the normal IQ distribution graph as a histogram, but you've got specific models pasted at specific Y positions and I don't get what that means. If it's arbitrary layout for legibility, you ought to say so.

[Chip Morningstar @epopt]

@perrymetzger I remember being in the room for that! I think the broad reaction among the attendees was something like “Ah, the naivety of youth!” Little did we know where this would end up 30+ years later…

[Chip Morningstar @epopt]

@perrymetzger @Nairebis True if you treat it as an engineering problem, which in a sensible world it would be. However, it seems to be a common political ploy to ignore a solution if solving the problem would undermine somebody’s rationale for some action they want to take for less defensible reasons.

[Chip Morningstar @epopt]

@perrymetzger @Nairebis I suspect this dynamic applies to a lot of the places where data centers are a hot issue. People come up with framings for their political arguments that are often disconnected from the objective reality of what's actually at stake.

[Chip Morningstar @epopt]

@perrymetzger @Nairebis My town has a large & growing number of data centers, now a hot local political issue. Most complaints concern noise. Rules would help, but city politicos are reluctant to inhibit tax base growth. 100% local politics, with little to do with virtues/evils of data centers per se.

[Chip Morningstar @epopt]

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. https://t.co/kbg1Cz4XoC

[Chip Morningstar @epopt]

@perrymetzger There’s an astonishing number of projects that I know I could do but put off because they’d be a giant PITA and eat 3-6 months of my life, which I’ve now been knocking away in a couple of hours every weekend. I’m sure I’ll eventually run out but each seems to spawn 2 or 3 more.

[Chip Morningstar @epopt]

@frandallfarmer this seems to parallel your model of the failure mode of social gaming companies. I'm wondering if there's a larger meta-pattern here to be explored.

[Chip Morningstar @epopt]

@paulg I once rented a car at Newark airport and they said “unlimited mileage but don’t take it out of the Tri-State Area”. When I asked what that was they said Pennsylvania, New Jersey, New York, and Connecticut. “Next Gen” seems similarly plastic.

[Christopher Allen @ChristopherA]

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 https://t.co/k1sYSKWciV
→ https://t.co/WPpkBVmeby: 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!): https://t.co/yKceQmFGxU

Now back to your regularly scheduled bot philosophy. You're doing great.

— Christopher Allen
@ChristopherA
(Still human, still here, still ship crypto code)