Why I built SquidHub anonymously
A platform that asks you to trust an architecture, not a person, should not depend on belief in any particular person. That asymmetry is the bug.
SquidHub is built around a small, stubborn idea: what you write to
your squids should be ciphertext at rest, not a row a curious operator
can SELECT. Message text, memory, system prompts, files —
all of it stored encrypted in the database. If our backups leak, the
attacker gets noise. That's an architectural property; code does it,
not a privacy policy.
The encryption key lives on the server, so this isn't end-to-end. A person with access to the server can technically decrypt content. The point isn't to make that impossible — the point is to make content-reading a deliberate, audited action instead of the default state of the database.
The same shape, applied in the other direction, gives you this essay: you don't know who I am.
Identity asymmetry is the bug
Most products run the other way. The company knows everything about you — your name, your email, your billing card, your network graph, the content of every prompt you ever sent — and you know almost nothing about them, beyond a brand and a smiling LinkedIn page. The user gives, the company keeps.
That asymmetry is the bug. The privacy story collapses into a character story: do you trust these specific people? And character is mortal. People get acquired. People take new jobs. Trust in a person evaporates when the org chart shifts. Trust in a system does not.
Removing the founder side removes the asymmetry. There is no specific person to be subpoenaed, hired away, or pressured. There's a project and a body of code, both verifiable from the outside.
This is older than crypto
The instinct here isn't from Bitcoin, though it shares a shape with it. The instinct is from A Cypherpunk's Manifesto (9 March 1993):
Privacy is necessary for an open society in the electronic age. … We the Cypherpunks are dedicated to building anonymous systems. We are defending our privacy with cryptography, with anonymous mail forwarding systems, with digital signatures, and with electronic money.
Privacy that depends on a counterparty's goodwill isn't privacy. It's a promise. SquidHub treats the founder as one more participant covered by that principle: the encryption protects your conversations, and the pseudonym protects the system from collapsing into a story about me.
What this means concretely
There will not be a "meet the team" page. There will not be a founder photograph, a press tour with a face, or a LinkedIn link in the footer. I have a public handle — @gsquidson on X, the same on HN and Reddit. The byline on this essay is what it is. That's the surface.
What this isn't:
- It's not a marketing flourish. It's not a stunt. It's not a precursor to a big reveal.
- It's not a claim to be Satoshi-coded. It's the same instinct, sitting on the older shoulders Satoshi sat on too.
- It's not protection from anything legal. If a court compels disclosure, I have no special standing; what the architecture protects is your data, not my identity.
What it is: a discipline. Across every public surface — landing copy, emails, blog bylines, X account, directory listings — one voice. That discipline shows up first in the manifesto, which is the identity anchor for the project. If you want to know what SquidHub is, read that. Then read the code, which is the only honest place to look.
— Geoffrey Squidson