Beeper Built the Inbox. Now Let’s Build the Town Square.

Last year I wrote about using Beeper and Matrix to bring comments home to WordPress. The idea was simple: a conversation about your post should not have to live on somebody else’s platform.

I still believe that. But I was thinking too small.

Comments are one room. What if Beeper gave us the whole building?

Discord proved that people want a persistent place online: channels, roles, live conversation, private rooms, voice, inside jokes and the feeling that the same familiar people might be there tomorrow. It also proved that millions of communities are willing to build their homes on rented land.

Beeper has the ingredients for a different answer. It already gives each user a Matrix identity, and Beeper’s own documentation says those accounts can talk with people in other Matrix communities. It already supports Matrix group chats. It already has polished apps on the devices people use every day. And since Automattic acquired Beeper, the same family of products now contains world-class pieces for publishing, identity, spam protection, commerce and messaging.

The perfect product is hiding in the overlap.

Call it Beeper Communities.

The missing half of Beeper

Beeper is brilliant at answering a personal question: Who is trying to reach me?

A community product answers a different one: Where do my people gather?

Those are not competing jobs. They are two modes of the same communication app.

Open Beeper and you would see a simple switch:

• Inbox is the Beeper we know: personal conversations from all your networks.
• Communities is a collection of shared places: OpenStation, a WordCamp group, a local club, an open-source project or a group of friends.

The first mode is organized around people. The second is organized around places.

Underneath, Communities would use the parts Matrix already has. A community is a Space. Its channels are rooms. Membership, permissions, encryption and federation use the protocol instead of being reinvented in a private database.

The technical nouns can stay underneath the floorboards. Normal people should not have to know what a homeserver is to join a gardening club.

What people understand	What Matrix provides
Community	Space
Category	Subspace
Channel	Room
Account	Matrix ID
Moderator and member roles	Power levels
Voice room	MatrixRTC
Invite	Matrix link with a friendly join flow

The product should feel as immediate as Discord, while the foundation remains portable, federated and open.

The version that needs Beeper’s support

Could someone build a third-party Matrix client that looks like Discord? Absolutely. Several people have tried.

But the magical version requires Beeper to participate.

Why? Because authentication is the difference between an interesting demo and a product people trust. In the perfect version, a Beeper user does not hand their password or encryption keys to an unknown community app. They tap Continue with Beeper, approve the new session inside Beeper and arrive with the identity they already use.

Beeper remains responsible for account recovery, device verification, encryption keys, push notifications and suspicious-session warnings. The community layer receives only the access it needs. If access is revoked, it stops working.

That is much better than asking users to paste homeserver credentials into a new website. It is also the kind of polished, boring security work that makes a new category possible.

The first-party experience could be almost frictionless:

1. A friend sends you an OpenStation invite.
2. The link opens in Beeper.
3. Beeper shows the community name, its homeserver, moderation policy, whether rooms are public and whether messages are encrypted.
4. You tap Join.
5. OpenStation appears under Communities, with no new password and no new app to install.

People who use Element, FluffyChat or another Matrix client should still be welcome. Beeper would be the best door, not the only door.

That distinction matters.

WordPress turns conversation into memory

Discord is excellent at now. It is terrible at later.

A useful answer disappears into a channel, is found once by search and then gets asked again two days later. Entire communities accumulate years of knowledge that the public web cannot link to, search engines cannot index and members cannot easily turn into something durable.

This is where Automattic has an advantage no chat startup can casually reproduce.

A Beeper Community could have a WordPress-powered public home. Not a marketing page bolted onto the side—a real front door for the community.

The OpenStation site could show its welcome guide, code of conduct, events, featured projects and selected public conversations. Moderators could turn a great support thread into a clean article. A weekly digest could summarize what the community built. A solved question could become an indexed answer with a permanent URL.

The live room remains alive. The useful parts become part of the web.

Automattic’s products could each do the job they are already good at:

• WordPress provides the public site and durable publishing layer.
• Gravatar provides a portable public profile, while still allowing a community-specific nickname.
• Akismet helps identify spam and coordinated junk before moderators drown in it.
• WooCommerce can connect memberships, events or supporter benefits to private rooms without making payment the identity system.
• Beeper provides the daily app, notifications and trusted Matrix session.

None of those integrations should be mandatory. Matrix communities outside the Automattic world should still work. But together they create something unusually complete: chat that knows how to become publishing, and publishing that knows where its community is talking.

OpenStation should be the first neighborhood

I would start with OpenStation because it is exactly the kind of community this product should serve.

The initial structure does not need to be clever:

• Start Here for the welcome guide and code of conduct.
• Announcements for releases and events.
• General for the daily pulse.
• Builders for people making themes, games and tools.
• Showcase for the delightful things people create.
• Help Desk for support that can later become public documentation.

New members with Beeper would join in seconds. Existing Matrix users could arrive from their preferred clients. Visitors could browse selected public channels on the OpenStation website before deciding to join.

That small launch would test every important part of the idea: onboarding, moderation, cross-client behavior, public archives, identity, notification overload and the line between a live conversation and a publishable artifact.

OpenStation would not be a fake showcase with empty channels. It would be the neighborhood where the product team has to live with its own decisions.

A business, not just a protocol demo

Open protocols do not eliminate the need for a business. They change what the business gets paid for.

Do not charge people for the right to hold their own identity. Charge organizers for making a community easier to run.

The free product could include public communities, standard moderation, basic voice rooms and federation. A paid Community Pro plan could add a custom domain, branded onboarding, larger media storage, advanced moderation queues, analytics, publish-to-WordPress workflows, membership automation and better support.

Larger organizations could pay for managed hosting, retention controls, compliance tools and professional migration from Discord or Slack.

The moat would not be trapping messages. It would be operating the best place to gather without trapping them.

That is a healthier bargain.

The hard parts become the right hard parts

Matrix does not magically solve community software. Large rooms still need to feel fast. Roles must be understandable. Voice needs to work every time. Public communities need serious tools for raids, harassment, appeals and federation policy. Discovery must help good communities grow without creating a spam directory.

Those are difficult problems.

They are also product problems worth solving.

With Beeper’s support, the team would not begin by rebuilding encrypted messaging, cross-platform clients, session management and an open protocol. It could concentrate on the human layer: making a room feel welcoming, helping moderators keep it healthy and letting a good conversation outlive the scrollback.

Beeper has described its long-term goal as helping move chat toward an open standard. Communities would make that promise tangible. People would not choose Matrix because somebody lectured them about federation. They would choose a great community, tap Join and discover later that the door was never locked behind them.

From inbox to town square

Discord built a very good rented stadium. Beeper and WordPress could build a town square.

One app would handle the conversations sent directly to me and the places where I choose to belong. One identity could move between them. A community could have the energy of live chat, the permanence of a website and an exit door that actually works.

If this idea came up at dinner, Teddy would probably cut through my whole pitch with one question: Why would Beeper do it?

Because Beeper already built the hard part. Because Automattic already knows how communities publish, earn money and survive on the open web. And because the next great communication product may not be another inbox.

It may be the place on the other side of it.

---

Disclosure: This is an independent product concept for discussion. It is not an announced Beeper, Automattic, Matrix or OpenStation product.