Reading an article is one thing. Knowing how the wider dev community reacted to it is another. Community take pulls that conversation into the post itself.
<h2>Here’s what’s new</h2>
<ul>
<li>TL;DR of the discussion: A plain-English summary of what developers are actually saying, right on the post.</li>
<li>Sentiment breakdown: A quick bar showing how opinion splits between positive, mixed and skeptical.</li>
<li>Deep dive: Expand to see the case for, the pushback, how each community leans, the hottest debate and the questions people are still asking.</li>
<li>Real quotes with receipts: A few standout comments, with author, platform, engagement and a link straight to the original thread.</li>
<li>Sources you already trust: Takes are aggregated from external developer communities like Hacker News and Lobsters, with links back to every thread.</li>
</ul>
<h2>See it in action</h2>
Take <a href="https://daily.dev/posts/firefox-is-now-the-last-major-browser-that-still-supports-ublock-origin-dqtsnxc3h" target="_blank" rel="noopener nofollow">Firefox is now the last major browser that still supports uBlock Origin</a>. That story pulled over 1,000 comments across Hacker News and Lobsters. Instead of reading all of them, the take gives you the read in one line: most developers see uBlock support as a genuine differentiator, plenty think Mozilla should just build ad-blocking in natively, and a vocal minority does not trust Mozilla’s motives at all. The breakdown lands at roughly 45% positive, 35% mixed, 20% skeptical, and the flashpoint is called out for you: does refusing to bake in ad-blocking undermine Mozilla’s user-first reputation, or is it the reasonable call?
<h2>Not every post gets one</h2>
Community take only shows up when there is enough real conversation to summarize. A post needs a meaningful volume of comments across external discussions before a take is generated, so you will see it on stories that sparked genuine debate and not on quiet ones. Most posts in your feed will not have one, and that is the point.
If the discussion keeps growing, the take refreshes to reflect it. If a post never picks up conversation, no take appears. A summary of three comments is not a community take, it is just three comments.
<hr>
Tell us what you think. If a take feels off, or you spot a discussion we should be pulling in, we want to hear it.

Star

Get the latest product updates and announcements about daily.dev

daily.dev Changelog

Daily.dev introduces Community Take, a feature that aggregates developer discussion from external communities like Hacker News and Lobsters into a summary attached to each post. It includes a TL;DR of the conversation, a sentiment breakdown (positive/mixed/skeptical), a deep dive with arguments for and against, standout quotes with links to original threads, and links back to source discussions. The feature only appears on posts with substantial external conversation volume and refreshes as discussion grows.

Community take: see what other developers think about a post

That’s awesome!
<img src="https://static.klipy.com/ii/2711dd8a75a85be822d136ec94899b3f/1f/e2/RyrvXnzx.gif" alt="GIF">

Amazing!! Can’t wait to have a try

awesome sounding feature!
maybe im a little slow but how excatly do we get to see the community take feature in action for the applicable posts?