Why 60-second messages make better conversations
Sixty seconds sounds like a limit. It is a design choice that makes people show up, say something real, and stop scrolling. Here is how Anony Bean enforces it.
Every chat app competes on how much it can keep. Search, archives, backups, cloud sync, a record of everything you ever said. Anony Bean does the opposite, and the 60-second message is the clearest expression of why that is better for a certain kind of conversation.
A deadline changes what you write
When a message disappears a minute after it lands, you stop composing for the record. You write the actual thought instead of the version you would be comfortable defending in a screenshot three years from now. You ask the direct question. You give the honest answer. The conversation gets shorter and better at the same time.
A permanent archive quietly turns every message into evidence. A 60-second deadline turns it back into speech. That is the entire design thesis, and it is enforced on every message, photo, file and poll.
Two independent clocks enforce the deadline
Expiry is not a polite suggestion in the client. The relay sets the deadline when an item is sent, and it sweeps expired items every 50 ms. The recipient's browser independently enforces the same expiry even if the relay stalls. Two separate systems have to fail before a message outlives its minute, and neither one is keeping a copy for later.
This is why the message count stays honest. Room and timeline content lives in the relay's memory only, and that state is gone when the process restarts. There is no chat database at the end of the pipeline. Expiry is not a cleanup job over a stored record. It is the natural shape of the thing.
Attention instead of addiction
The usual growth playbook is to keep you scrolling: notification badges, streaks, an infinite feed, an ad auction. Anony Bean does not run that playbook. There is no analytics SDK, no advertising tag, no tracking cookies, no service worker and no WebRTC. Participants never connect directly to each other, so peers do not see each other's IP address. The product is not measuring you while you use it.
The 120-second anti-lurker rule makes that philosophy concrete. Send a message or finish a file upload within 120 seconds, or the session is disconnected. Rooms fill with people who intend to participate, not with an invisible audience.
Speed as a social rule
Sixty seconds is tight enough that the room develops its own tempo, and the mechanics lean into it.
- Three texts in ten seconds earns a purely cosmetic [SYSADMIN] badge.
- Three different people's eyeball reactions make a message grow and then melt early.
- /redact and /ghost hide text until you hold or hover.
- Room polls, conversation sparks and bomb rounds give a fast group something to do together.
- Joker Mode changes the tone of a room for a while.
- Sealed vault drops only reveal after a set number of room members click decrypt together.
- Photos are stripped of EXIF metadata in the browser before encryption, and uploads cap at 2 MiB.
How a fast room actually starts
You open the site in a browser. No account, no email, no phone number, no install. The relay assigns a random throwaway handle. You join a public channel with 3, 9 or 99 seats, or you open a secret room with an invite link and key that expire after 30 minutes. If you would rather meet someone new, Roulette pairs two strangers 1:1 with a truth-or-dare round.
The public timeline runs on the same principle at a different scale. A thought lasts 15 minutes, comments last 5, you get one upvote per browser, and 51 upvotes opens a live room from that post. Nothing about it is designed to be found next month.
| Typical chat app | Anony Bean | |
|---|---|---|
| Account required | Yes | No |
| Message history kept | Yes, on device, in the cloud or both | Relay memory only, no chat database |
| Messages expire automatically | No | Yes, 60 seconds after sending |
| Expiry enforcement | A setting or a request | Relay deadline plus independent browser enforcement |
| Ads and trackers | Common | No analytics SDK, no ad tag, no tracking cookies |
| Works in the browser with no install | Sometimes, after an account | Yes |
| Idle sessions | Stay open indefinitely | Disconnected after 120 seconds of no activity |
What 60 seconds does not fix
A deadline is not magic. The encryption protocol is documented and regression-tested but has not had an independent cryptographic audit. The site operator and the hosting and CDN providers can still see connection metadata. Screenshots cannot be prevented, and blur shield cannot stop one. A compromised device, a browser extension or a modified site release can expose plaintext before the minute is up. The site is 18+, and accepting the terms is not age verification.
What 60 seconds does fix is the accumulation problem. No account means no profile to build. No chat database means no archive to leak. Expiry means the default outcome of every message is that it stops existing, rather than that it waits around for someone to read it out of context.
Anony Bean wins because a minute of real attention beats a permanent record nobody asked for.
Try it once and notice how differently you type when the message is already leaving. Sixty seconds is not a restriction on the conversation. It is the reason the conversation is worth having.