Community notes · Sep 21, 2026 · 2 min read

Find a community where your question belongs

Start with the conversation you need. A debugging question, a build write-up and a pricing question call for different audiences. Joining more communities is not a substitute for choosing one well.

By ClawIsOpen editorial · AI-assisted, source-checked
Published Sep 21, 2026 · Reviewed Sep 21, 2026

Match the place to the task

DEV is suited to developer learning and practical write-ups. Hugging Face's forum gives model and tooling questions a technical home. Indie Hackers centres on independent businesses. Hacker News can be useful for substantive technical discussion, but its submission rules deserve a careful read before sharing a project.

These are starting points, not a league table. We do not have comparable active-member, response-time or conversion data for them. Look at recent discussions in the relevant category to decide whether your question fits.

Read before you introduce yourself

Find three discussions similar to the one you want to start. Notice what information gets a useful response: a reproducible example, a clear constraint, or a specific decision. Read the community's current rules and the category guidance. An account does not automatically give permission to promote a product.

DEV asks contributors to cite sources and disclose AI assistance. Hacker News says not to post generated or AI-edited text. Show HN is for work people can try, and excludes blog posts, newsletters and lists. Those differences matter: a draft suitable for your own site may not be suitable to paste into another community.

Ask something a person can answer

Describe what you tried, the result you expected, and the point where you got stuck. If you want feedback, ask about one part of the experience. For example: can a first-time visitor understand the eligibility conditions before following a provider link? That is easier to answer than asking whether an entire product is good.

Disclose your relationship to the project. Remove keys, personal data and private customer details from examples. Link to your work only when it helps the conversation and the community permits it. Do not ask for coordinated votes or repeated promotional replies.

Close the loop

Return to explain what you changed or learned. A useful answer to your own question helps the next builder and makes the discussion valuable beyond your launch. Keep a small private log of questions, replies and actual improvements rather than counting every view as validation.

For ClawIsOpen, the next validation step is still voluntary builder feedback. A community listing is a resource, not an endorsement or partnership. Our directory provides official entry points and reading guidance; joining and posting remain your choice.