In the early web, publishing something online was frictionless. You had a personal webpage, a guestbook, a forum post. Many of these required no registration. You just wrote something and it was there.
Somewhere along the way, “create an account to continue” became the default for almost every platform. It’s so normalized now that asking why feels strange.
But it’s worth asking.
Why accounts became mandatory
The shift happened for business reasons, not technical ones.
Accounts enable retention, if you have an account, the platform has a reason to send you notifications, emails, and reminders to come back. Without an account, you’re just a visitor they can’t reach.
Accounts enable advertising, a logged-in user with a profile and history can be targeted with much more precision than an anonymous visitor. The account is how platforms build the profile that makes their advertising product valuable.
Accounts enable growth metrics, registered users is a metric that matters to investors. Monthly active accounts, user growth, retention rate, these require accounts to measure.
Accounts reduce spam and abuse, this is the one legitimate technical reason. Accountability reduces some forms of misuse. But it also introduces friction that drives away legitimate users.
The honest picture is that most platforms require accounts primarily because it serves their business model, not because it serves you.
What mandatory accounts actually cost
Friction, every additional step between “I have something to say” and “I said it” loses people. Email verification, choosing a username, confirming you’re not a robot, all of this is friction that filters out casual contributors.
Identity attachment, everything you post under an account is permanently tied to that identity. This changes what people are willing to say. The absence of anonymity is a form of self-censorship.
Data, creating an account means giving the platform your email, often your phone number, and agreeing to terms that let them use your content and behavior data in ways you may not have read carefully.
Platform dependency, your content lives in their system under their rules. Platforms change, get acquired, shut down, or change their policies. Content on platforms you don’t control is always at risk.
What no-account publishing looks like
It used to be common. Some platforms still do it.
Telegra.ph (from the Telegram team), open a URL, write, publish, get a link. No account. It’s been around since 2016 and still works this way.
Pastebin’s original model, paste text, get a link. The account option adds features but isn’t required.
The pattern is: content + link, no identity. The content stands on its own.
Echo, what I built for this
I got frustrated with the friction of wanting to publish something without it being tied to my main identity or requiring a platform signup. So I built Echo.
The flow is: go to the site, write, hit publish, get a link. That’s it. No email. No username. No password. The post exists at a URL. Share it however you want.
The technical challenge, and the interesting design problem, is how you handle editing and ownership without accounts. Echo uses a local browser key that’s generated when you publish. That key is what lets you edit or delete later. It’s tied to your browser session, not to a registered identity.
The tradeoff is that if you clear your browser storage, the key is gone. You can still read the post publicly, but you can’t edit it. I’m still thinking about the right solution to this that doesn’t require an account.
It’s still in development and the testing phase is running until August 2026. Early users get pro features while it’s in beta. Honest feedback on what’s missing or broken is genuinely useful.
The broader point
The account requirement isn’t inevitable. It’s a design choice that reflects platform incentives more than user needs.
There’s a version of the internet where more publishing, sharing, and communication happens without mandatory registration. It would look more like the early web in some ways, more ephemeral, less tracked, less monetized.
Whether that’s better overall is a separate debate. But the option should exist for people who want it, and it mostly doesn’t right now because there’s no business incentive to build it.
That’s the gap Echo is trying to fill, at least for writing.