The upvote changed everything
Three weeks after we launched Feedr, a church pastor in Manchester sent us a message. 'I asked my congregation a question about faith and doubt. Forty upvotes on one comment. I'd never have known which answer actually landed without seeing the numbers.' That single message shaped how we think about live audience interaction.
Why a comment stream alone isn't enough
When we first built Feedr, it was just a stream. People typed comments in real time. That's genuinely useful. A lecturer can see what's confusing people. A podcast host can spot which jokes landed. But there was a problem we kept hearing from beta testers: if you have thirty people commenting, how do you know which comment actually matters to the room?
A conference speaker told us: 'I'm on stage answering a question and three new comments come in at once. I pick one at random because I have no way to know if that person's question speaks to the whole audience or just them.' That's when we knew upvoting wasn't a nice-to-have. It was foundational.
The moment upvotes made sense
We added upvoting to the free tier because we realised something: if your audience has no say in what gets amplified, you're missing the whole point of real-time engagement. With upvotes, the room self-moderates. Comments that resonate rise to the top. Comments that don't, fall away. It's democratic in a way that a single moderator's eye can never be.
What surprised us was how fast audiences understood it. You don't need to explain upvoting. People know from Twitter, from Reddit, from every comment section they've ever seen. They get it instantly. A host runs a session, opens the comment stream in the Feedr app on their phone or tablet, and the audience in the browser sees the same stream. They type. They upvote. The highest-voted comments bubble up. The host can see exactly what the room cares about.
Moderation without friction
Here's what we didn't expect: upvoting is a moderation tool. When someone posts something off-topic or unkind, audiences downvote it mentally with their silence. The good stuff rises. The noise falls. That's not perfect, but it's better than a host trying to police thirty voices at once while they're in the middle of speaking.
That said, we built actual moderation tools into the Creator and Pro tiers because some sessions need more control. You can set a moderation queue, which means comments don't go live until you approve them. You can pin comments. You can invite a guest moderator to help manage the flow. But honestly, most people just use upvoting. It works. The audience polices itself, and the host stays in the conversation instead of playing referee.
The number nobody talks about
After a few months of live sessions, we noticed something in our session reports. Hosts were checking which comments got the most upvotes, then following up with the person who posted them. A lecturer in London wrote: 'One student asked a question about my research that got twenty-three upvotes. Turns out it was something I'd been trying to explain badly for weeks. That upvote count showed me exactly what I needed to rethink.' That's not engagement theatre. That's actionable feedback.
The upvote count also matters for the audience member posting. If you comment and get one upvote, that's just someone liking your joke. If you get fifteen, suddenly you feel heard. You feel like your question or your idea mattered to the room, not just to the speaker. That's the real value. It's not manipulative. It's genuine recognition.
What we got wrong at first
We initially capped upvotes on the free tier, thinking people would upgrade to get unlimited voting. We were completely wrong. We removed the cap because it made the feature pointless. If upvoting is the entire mechanism for showing what matters, you can't limit it. That would be like limiting how many times people can actually raise their hand at a conference.
The free tier is three sessions a month with up to a hundred people. That's genuinely free, genuinely useful. A lecturer can run a semester's worth of sessions. A guest speaker can test it out before a bigger event. And upvoting works exactly the same way. There's no crippled version where votes don't count or disappear. We learned early on that half-features are worthless features.
Who actually uses this
We built Feedr for anyone who stands in front of people and wants to know what they're thinking. Conference speakers, obviously. But also preachers. Lecturers. Podcast hosts who want to see what their live audience is reacting to. Event organisers who need Q&A that doesn't require everyone to download an app or log in to an account. Audience joins via a QR code. That's it. Browser. No friction. They comment and upvote in seconds.
The person running the session sees everything on their phone or tablet. They can pin a comment that needs visibility. They can moderate if they upgrade. They can see a report after the session. But the core engine is that live stream with upvoting, and it works for everything from a church in Manchester with forty people to a tech conference with five hundred attendees.
Upvoting isn't a feature. It's how you let an audience tell you what actually matters. The question isn't whether you should use it. The question is what you're missing right now by not hearing your audience this clearly.