... changes what you see when you open a person. The chat view put every message in one line, as if each one answered the one above it. With several threads going at once, or several people in one, that was often wrong, and I kept losing track of who was answering what. So I rebuilt the view around threads

... free as always. What's new: A whole new look. The panel now has three bands: Waiting on you at the top, then Working, then a Resting shelf where finished pets relax. Pets that come to you. When a thread needs you, click its pet: you're taken straight to that thread

... profile, nothing clever. Under product launches: 14 comments. 0 upvotes, 0 replies. All 14. Some of them were long and specific, one quoted the maker's own line and asked about a real trade-off. Nothing. In forum threads: 22 comments. Most got 1-2 upvotes within hours. One turned into a back-and-forth with the thread

... people we love to communicate with, interact with, or simply follow. From my very first day on Product Hunt, some people became little lighthouses for me here. The moment I signed up, I noticed @busmark_w_nika and her threads. She became one of those people I always enjoy following here. Then came @amraniyasser and @bengeekly . And that was only my first day =D I always enjoy seeing comments from @byalexai , @rabnoor_s , @samran_elahi , @dzaitzow and @yelyzaveta_kibets under ... ... threads

... playbook was always the same: buy a list, write a cold email, hope it lands on the right day. It rarely did. Meanwhile, the people who actually needed a solution were posting about it on Reddit, in detail, in threads nobody on the sales team was reading. So I built ThreadPilot . Screenshot attached: it's an alert for a thread

... place: the TUI tab. If you wanted your unread notifications in a status line, a cron job or a morning summary, you were back to gh api /notifications, and to redoing what the tab already does: sorting threads GitHub doesn't return in time order, and turning API URLs into links you can actually open. octoscope 0.37.0 adds --inbox to the scriptable side. octoscope --plain --inbox adds an Inbox section to the summary: when, why (review_requested, mention, ci_activity ... ... what kind of thread

... noticed something across a few threads I've posted here. The ones where I jump back in and reply to early comments seem to stay active longer, more people join in, more replies stack up. But then I've also seen threads

... spent an hour writing a thread I was sure would spark discussion. Polished. Clear. A good question. Nobody replied. |Then I posted something almost by accident. A messy observation about something I was stuck on. No structure. No point. Just a half-formed thought. That one got replies. Real ones. People sharing their own experiences. A conversation. I think the polished ones signal "I have this figured out, come admire my clarity." The messy ones signal "I'm actually stuck ... ... help me think." People respond to the second one. Have you noticed this too? Do your best threads

... thread rejected recently, still not fully sure why. Got me wondering about a few things and figured i'd just ask directly instead of guessing. Does getting a thread

... lucky to get 2 3 comments. Comment from Rabnoor Singh(@rabnoor_s): one thing id add, and it cuts across the follower point. the hour you submit isnt the hour it goes live, because approval sits in between. two threads written the same morning can land eight hours apart, and the later one reads like it failed on content when it actually failed on the clock. someone here measured that gap in another thread

... Something I've run into repeatedly and I can't tell whether it's the platform, my settings, or just me. I found a comment on my own intro thread that had been sitting there 20 days. It was the most useful piece of feedback anyone has given me on this platform, someone had taken the time to pull apart my positioning properly, and I only saw it because I happened to be scrolling my own activity. No notification appeared ... ... with two people who tagged me on launch day. So I was three weeks late to both. On the other hand, when a notification does arrive and I tap it, it often drops me at the top of a thread

... Same effort every time, same comment, just a different thread each time. The spread came entirely from which thread

... digest to my Notion." What lands in Notion example Tue Aug 12 Needs you today PR #481 approved overnight waiting on your merge Nina asked in #product whether the pricing page ships this week 2:00pm Northwind call proposal thread summarized below From then on, when you sit down at 9:00, the things that need you are already standing in line. Example 3: The end of the frantic ten minutes before a meeting (Outlook + OneDrive) Digging through email ... ... context ten minutes before a call is a workplace tradition nobody asked for. Cancel it: "Before my 2pm with Northwind pull the latest thread

... Pulled my own kitty points breakdown again since it moved a lot since the last time I checked. Sitting at 388 KP total now. Forum Threads plus 272, Comments plus 101, Reviews plus 10, Maker plus 6. Ten days ago Forum Threads

... same comment through four threads over a month and only one kept generating views weeks later. The difference was not the reply count in the first hour, all four got at least one. It was whether a third person with no connection to me or the OP joined within the first two or three days without being asked. If it stays just me and the OP going back and forth, that is engagement, not compounding. The one thread

... most reaction wasn't a pitch. It was the founder admitting a real gap straight up, saying a part of the product wasn't built well yet. That pulled more replies than any feature announcement in the same thread. The founder answered nearly everything within minutes, including comments that pointed out real problems, and never got defensive about it. The speed plus the lack of spin seemed to matter more than what the answer actually said. The first comment ... ... brand new thread

... Built this over the last few weeks of putting the same effort into different threads and watching some go nowhere. Check the OP's reply history first. If they never reply to anyone on their own thread

... discussion threads rejected on Product Hunt, and I'm genuinely curious about the review process. I understand maintaining quality, but I'd love to know what usually leads to a rejection. Is it the topic, wording, or something else? For those who've had threads

... than just launch day. If you approach it strategically, it can become an ongoing marketing channel rather than a one-day event. This is roughly how I use it: Talk about the product before launch through discussions, comments, and threads to build awareness naturally. Meet people through discussions and invite interested members (or potential users) to test the product, share feedback, and build relationships with them. (Many of them became part of my LinkedIn community too.) Improve the product based ... ... Product Hunt to get your product noticed (besides launching)? Comment from Venkat A(@venkat_a2): @bharatlearner  Your numbers match mine almost exactly, which is mildly depressing given we clearly got there separately. My own thread

... platform social distribution. One trend I ve noticed across several recent launches is how unpredictable post reach has become. A launch update that completely flops on X might get huge engagement on LinkedIn, or spark great technical discussions on Threads. Because user behavior varies so much across networks, cross-posting across all three seems necessary to capture full reach, though it has some friction points: Re-formatting overhead: Adapting the same core update across different interfaces takes time away from ... ... conversations: Once posts are live, keeping track of where discussions are taking place across platforms gets fragmented very quickly. For those actively promoting their startups or launches on socials: Do you cross-post identical updates to LinkedIn, X, and Threads

... Went through my notifications today and found what looked like two separate unanswered messages from the same person on the same thread. Both showed up in the notification list looking equally new. Opened the actual thread

... anyone new: Scribble tracks which sources AI engines cite when they answer questions. After 7,000+ citations across ChatGPT, Perplexity, Gemini, Copilot, and Claude, one pattern would not go away: the sources are rarely brand websites. They're Reddit threads, Quora answers, LinkedIn posts, Medium pieces. People talking about brands, not brands talking about themselves. Which means the conversations happening today are the citations of tomorrow. If your brand isn't in them, you're not in the answers either ... ... Conversation Radar. It crawls 6 platforms (Reddit, Quora, LinkedIn, Hacker News, Medium, dev.to ), finds the live conversations relevant to your brand and category, tags each one as a Question, Discussion, Problem, or Comparison, and links you straight to the thread

... biggest bottleneck. Is it... Finding users? Retention? Distribution? Pricing? Building fast enough? Curious to see what most founders/Builders are struggling with today. Comment from Abdullah Javaid(@abdullah_javaid3): @somesh_putatunda  Yes, ones with a number in them. A thread I started today with four specific view counts pulled in two people with their own counter data within hours. A pure opinion question in the same forum barely gets a reply from anyone but the OP. Comment from Ethan Cheng ... ... somesh_putatunda  Actually yes. The earliest signal shows up before the third person ever appears: someone asking a question back instead of just reacting. It happened right here with your first reply, and looking back most of the threads

... launch went live at 12:01 PT today. As I write this it is in single digits, nowhere near the featured cutoff. I would rather post the number than a vague "lots of learnings" thread, so here it is, plus what I actually think went wrong and what I am doing about it in the open. What was ready: product worked, landing page up, payments live, guidelines followed, assets done. Every readiness item on a standard launch checklist was ticked ... ... today, I think it is two specific things, and neither of them is upvotes. One, people who have had an actual back-and-forth with you. Not people who follow you quietly. People who argued with you in a thread

... reason has to come from somewhere else entirely. What I want from anyone who has shipped more than once: did your upcoming page ever produce followers on its own, or did every single one come from a thread, a newsletter, or a specific person? If it's the second, putting the page up early is still fine, it's just not the step people think it is. Real numbers welcome, zero included. Comment from Rabnoor Singh(@rabnoor_s): Zero included ... ... asked. I have an upcoming page live right now and its followers are 8, every one of them traceable to a person or a thread