BlindPost
The earliest version of BlindPost did one thing: let two people talk without anyone in the middle reading. Then groups. Then groups of 100,000. The throughline was always the same — make the server architecturally unable to see what you said.
Now we're adding channels — the broadcast side of the same coin.
A channel is where you write to many readers at once. A travel journal. A small newsletter. A study group's announcements. A single artist publishing pieces to their fans. The shape — one author, many subscribers — is what Substack and Telegram channels look like. The choices about who gets to silence you are different.
Why broadcast, on a privacy messenger?
Private speech alone isn't enough. People who care about privacy usually also care about not being silenced. The two come together: you want to choose who hears you, AND you want to know nobody can take down what you wrote because they disagreed with it, because they had subpoena power, because they bought the platform.
Most "broadcast" surfaces on the internet are built around a moderation pipeline. Channels on BlindPost are built around the opposite assumption: there is almost no moderation lever to pull. Our server doesn't keep a subscriber list, doesn't know who runs a channel, and doesn't track per-channel engagement. We can't read your posts, and we can't selectively delete or edit a single post or comment. The one lever that does exist is blunt — declining to relay an entire channel or account at the network level, reserved for clearly illegal content or legal compulsion — and even that is forward-only: it stops the next post, it can't rewrite or remove what subscribers already hold.
How it stays BlindPost
The encryption story doesn't change. A channel is still a public-key identifier. Your topic posts are still encrypted blobs, indistinguishable from any other group message. Comments on a topic ride the same end-to-end encrypted pipe. Likes are local-converged signals — counts tally on each subscriber's device based on the signals they've seen, not on a tally the server maintains.
We don't issue you a subscriber count from the server. We can't tell you "this post got 1,243 reads." We don't know. What we do show is the reactions and comments your readers chose to send back — those they sent, you see.
What channels intentionally can't do
A few things, on purpose:
- Nobody — not even the channel owner — can retroactively delete or edit someone else's comment. Each person owns their own words. Moderation is forward-only: kick a commenter so they can't write more, but their past writing stays in the thread, attached to their identity.
- There is no algorithm choosing what your readers see. Subscribers pull, in order, what you published.
- There is no "trending." No server is in a position to rank, weigh, or amplify. What spreads, spreads because someone forwarded it.
- No engagement-bait signals. Post-level read receipts don't exist — we don't know who read what, and we don't want to.
These omissions are features. If you want to build a writing surface on top of a privacy substrate, the things you skip matter as much as the things you ship.
The thesis
Channels: a microphone of your own.
A microphone you didn't have to ask permission to hold. A microphone that broadcasts your words, not our ranking of them.
If that's the kind of surface you want, BlindPost channels are live in the latest app update. Open the chat list, tap +, pick Channel.