Built an ephemeral chat app with zero accounts and zero stored history.
Stateful ratchets broke on late-joining peers, so I rebuilt the Nullstate Protocol: secret key stays in the URL hash + fresh 12-byte IV per message. Even my relay can't read it.
Link in reply 👇
Honest UI feedback needed for Phantom Chat:
Built a mouse-interactive 3D node globe behind the hero + a live self-destructing chat demo below.
You can't feel the 3D drag in a screenshot, so try spinning it on desktop—clean or too distracting?
Link in reply 👇
Solo-builder headache of the week: aggressive link-preview bots eating through my daily free-tier database writes before real humans even join a room.
For devs running serverless apps on $0 budgets—how are you filtering crawlers without blocking legit users?
Link in reply
Most privacy apps still ask you to trust their servers not to log your IP, phone number, or social graph.
Real privacy means building software where the server literally cannot read your messages—and doesn't even know who you are.
Link in reply 👇
You can't leak a user database that doesn't exist.
Instead of storing accounts, phone numbers, or chat logs, Phantom Chat keeps the secret key strictly in the URL #hash and wipes rooms on timer expiry.
Zero stored identity means zero breach surface.
Link in reply 👇
Most people don't realize how fragile stateful encryption ratchets get in browser group rooms.
One dropped packet or late peer join breaks sync.
Under the NullState Protocol, each message carries a fresh 12-byte IV—zero sync state needed.
Link in reply 👇
Try spinning up a room in 2 seconds (no login, no app install): https://t.co/a7Beq4DCKP
Full NullState Protocol architecture and /trust threat boundaries are documented on the site.
Try spinning up a room in 2 seconds (no login, no app install): https://t.co/a7Beq4DCKP
Full NullState Protocol architecture and /trust threat boundaries are documented on the site.
I've been building Phantom Chat solo to make ephemeral messaging truly zero-account—keys stay strictly in the URL #hash and nothing is stored on a server.
Still early, so if you have 30 seconds to test a room and break things, I'd love your honest feedback.
Link in reply 👇
Built an ephemeral chat app with zero accounts and zero stored history.
Stateful ratchets broke on late-joining peers, so I rebuilt the Nullstate Protocol: secret key stays in the URL hash + fresh 12-byte IV per message. Even my relay can't read it.
Link in reply 👇
Just shipped Phantom Chat V2—an identity-less messaging terminal with a 3D WebGL UI and a native Node.js CLI.
Instead of accounts or server-side keys, peers derive symmetric keys locally from the URL hash and decrypt via a fresh 12-byte IV per message.
Link in reply 👇
People think building a privacy app means expensive servers.
Reality: stitching Cloudflare Pages, Workers KV, and Firebase RTDB free tiers together so when one daily write limit hits, the backup takes over seamlessly without dropping a single user.
Link in reply 👇
Built an ephemeral chat app with zero accounts and zero stored history.
Stateful ratchets broke on late-joining peers, so I rebuilt the Nullstate Protocol: secret key stays in the URL hash + fresh 12-byte IV per message. Even my relay can't read it.
Link in reply 👇