I spent 6 months solo-building a Reddit where every post is a live chat room
Hi IH 👋
I'm building Angryecho — a community platform where every post is a real-time discussion room.
Not async comments you refresh. Not a Telegram group you have to create first. You open a post, and you're in a live room with everyone else talking about the same thing.
The insight that started it
I kept noticing the same pattern:
On Reddit or old-school forums, hot topics get thousands of comments — but everyone is talking past each other, not with each other.
On Weibo/Twitter, discussion gets scattered across feeds.
On Telegram/WeChat, you have to create a group and share a link just to discuss one piece of content.
Meanwhile, when something big happens — a game launch, a breaking news story, a product release — people don't want to "post a comment and come back tomorrow." They want to be in the room together, right now.
Threads proved one piece of this: people care when likes update in real time.
I wondered: what if the entire post worked like that?
What I built
Angryecho is Reddit-shaped, but real-time:
Post = room — open a post, enter instant discussion, chat with everyone there live
Live engagement — like counts and interaction data sync over WebSocket without refreshing
Post insights — authors can watch engagement update in real time
Full community stack — feed, comments, voting, DMs, search, rich text, notifications
Live demo: https://www.angryecho.com
The hard part (for fellow builders)
The product idea is simple. The engineering isn't.
I spent ~6 months full-time as a solo founder to get an MVP live. Stack:
Frontend: Nuxt 4, Vue 3, Pinia, Tailwind
Real-time: WebSocket + STOMP for live chat, for live counts)
Backend: Java + Rust for the real-time layer
The tricky bits:
"Post as room" architecture — treating a single piece of content as a real-time channel, not just a comment thread
List view + detail view both need live data — likes updating in the feed while you're scrolling, chat updating inside the post
Message ordering, dedup, reconnect — the unsexy stuff that breaks trust fast if you get it wrong
I'm still early. Moderation tooling isn't done yet. Mobile apps are on the roadmap. No revenue — I'm focused on getting the core experience right first.
Who this is for (starting narrow)
I'm not trying to be "Reddit but bigger" on day one.
First communities I'm targeting:
Indie hackers / builders — ship logs, "roast my landing page," launch-day threads where people actually talk in real time
Hot-topic verticals where synchronous discussion matters: games, tech, live events
The indie dev angle feels especially natural here: post your project → instant feedback room opens → no need to spin up a Discord just to collect reactions.
Where I am now
✅ Web MVP live with real-time chat + live likes
✅ Core community features working (feed, DMs, search, rich posts)
🚧 Moderation, mobile, growth — next
Honest ask
I'd love feedback from this community specifically:
Does "post = live room" click for you, or does it feel like noise?
Would you use this for launch posts / build-in-public updates instead of IH comments + Discord?
What's the one thing that would make you come back to a new community product?
Happy to answer questions about the real-time architecture or the solo-founder build process.
I think the interesting question isn't whether people want real-time chat—it's whether a conversation should become synchronous by default when enough people care at the same time. That's a very different bet from building another community platform. I'd pay close attention to which topics naturally create that "everyone wants to be here now" behavior, because that feels like the wedge rather than trying to replace forums broadly.