Read the Room: Community Rules Before You Share

A launch needs an audience, and audiences live in communities: forums, chat groups, discussion sites, newsletters with comment sections. These places are run by people who built them for something. If you walk in and start shouting about your product, you are likely to be removed, ignored or remembered for the wrong reasons.

The fix is simple, if slow. Read the room before you speak. This guide shows how to find the rules, how to read the unwritten ones and how to share in a way that earns a welcome.

Why rules exist

Communities make rules because they have been burned. Too many promotional posts push out real conversation. Too many vote requests make rankings meaningless. So most places write down what they want and what they do not.

You can see this in the guidelines of big sites. Hacker News, for example, says in its general guidelines that the site should not be used primarily for promotion, that it is fine to post your own work part of the time, but that the main use should be curiosity. It also asks people not to automate posting and not to put generated text in posts. Its separate Show HN guidelines describe what counts as a Show HN: something people can try, not a landing page or a sign-up form, and they ask makers to be around to discuss it.

Whatever you think of a given rule, breaking it costs you. The people who run the place decide what happens next.

Finding the written rules

Before posting anywhere, look for:

• A pinned post or banner at the top of the group.
• A sidebar or "About" section with a list of rules.
• A link labelled guidelines, FAQ, code of conduct or posting rules.
• A dedicated thread for self-promotion, sometimes weekly.
• The moderators' names and how to contact them.

Read all of it. It takes ten minutes and saves hours of embarrassment.

Look for these common rules in particular:

• Is self-promotion allowed, and where?
• Is there a ratio, such as only posting your own work a small share of the time?
• Are referral links, affiliate links and tracking links banned?
• Is asking for votes or reactions banned?
• Are there format rules for titles?
• Are certain days or threads set aside for launches?

Reading the unwritten rules

Every community also has habits that are not written down. You learn them by watching.

Spend a week reading before you post. Notice:

• The tone. Formal, jokey, technical, gentle?
• What gets praised. Detailed breakdowns, honest failures, helpful answers?
• What gets criticised. Hype, vague claims, thin posts?
• How promotional posts are treated. Welcomed with curiosity, or met with eye-rolls?
• Who the regulars are. Whose replies carry weight?

The community's own best posts are your template. If the most appreciated launch posts include a story of what went wrong and what you learned, write that. If they are short and technical, be short and technical.

Join in before you ask for anything

The most reliable way to be welcome is to be useful first. For a few weeks before launch:

• Answer questions you actually know about.
• Share useful articles or tools that are not yours.
• Give honest, kind feedback on other people's work.
• Say thank you when someone helps you.

Do it because you want to take part, not as a trick. People can tell the difference, and a member who has been helpful for months gets a very different reception from a brand-new account posting a link.

Remember, too, that your profile will be read. Many people click through to see who you are. Fill it in honestly: your name, what you work on, and a link to your site.

Posting your launch

When the time comes, follow these habits.

Use the right place. If there is a thread for launches, use it. If posts must be in a particular category, pick the right one.

Follow the format. Titles in the style the group uses. For places that dislike hype, avoid capital letters, exclamation marks and superlatives. Hacker News's guidelines ask people not to do things to make titles stand out and to avoid gratuitous numbers.

Be transparent. Say you made it. People respect "I built this" far more than a post pretending to be a neutral discovery.

Make it easy to try. The Show HN guidance asks for things people can try, ideally without barriers such as sign-ups or emails. The more friction you remove, the more feedback you get.

Explain the why and how. Tell the story. What problem? What choices? What went wrong? A post that starts a conversation is welcomed. One that only points at a link is not.

Be around. Stay for the discussion. Reply to every comment you can, kindly, including critical ones.

What not to do

• Do not ask friends to vote or comment. Some communities explicitly ban this, and it is easy to detect. A launch that rises through a pile of identical one-line comments looks fake and can be removed.
• Do not use extra accounts. Posting from alternate accounts to boost your own post is deceptive. It also breaks the rules of nearly every community.
• Do not repost the same thing repeatedly. If it did not land the first time, work out why before trying again, and check the rules about reposting.
• Do not spam many groups at once. Copy-pasted posts across ten communities look like spam, and moderators talk to each other.
• Do not hide referral or tracking links. Where they are banned, they are banned. Where they are allowed, say so.
• Do not argue with moderators in public. Contact them privately, politely.

When something goes wrong

If your post is removed, read the reason carefully. Often it is a formatting or placement issue and an easy fix. If the reason is unclear, send a short polite message to the moderators asking what you could change. Thank them for their time whatever the answer.

If your post is not removed but gets harsh comments, treat them as free feedback. Reply with thanks, correct anything factual and ignore pure unkindness. Read the comments again a day later with a clearer head. They often contain the best advice you will get.

If a discussion turns into a pile-on, step away. You do not have to win. Other members notice who stayed calm.

Honest sharing across several places

If you plan to share in more than one community:

1. Make a list with the rules summary for each.
2. Write a different post for each, in the local voice.
3. Space them out over days, not minutes, so you can reply properly everywhere.
4. Keep a note of who replied and what they said.

That is a lot of work, and that is the point. Fewer, better posts are better than a scatter of cold ones.

Communities for makers and founders

There are many places where founders share work. Some, like Hacker News, are broad and technical. Others, like the Indie Hackers community, focus on people building and running small online businesses and share stories and numbers. Each has its own habits: read the front page for an hour and you will see them. Netiquette, the old idea of courteous behaviour online, is still the best summary: remember there is a person on the other side.

A checklist

• You have read the written rules and watched for a week.
• You have taken part before promoting.
• You are posting in the right place, in the right format.
• You say plainly that you made it.
• It is easy to try.
• No vote requests, no extra accounts, no copy-paste blasts.
• You will be around to reply.
• You have a calm plan for criticism.

On this platform

The submit page is where you set up your own launch entry, and the launches page shows how entries from other makers read, a good way to see what a calm, honest description looks like. The categories page shows where similar products sit.

A worked example

Imagine you built a small tool that helps allotment clubs share a watering rota. You find a gardening forum with a weekly "what are you making?" thread. You read the rules: one post per project, no referral links, be honest about who made it. You spend two weeks answering questions about composting and raised beds. Then you post in the weekly thread: a two-paragraph note about why you built the rota tool after your own club's spreadsheet fell apart, a plain link, and a question about how other clubs handle holidays.

The replies are friendly, because you were already a face in the room. Two members ask for a feature, one points out a bug, and a moderator thanks you for following the thread rules. None of that happens if you arrive on day one with a headline in capitals. The product is the same. The welcome is not.

The short version

Communities are run by people with reasons for their rules. Read the written ones, learn the unwritten ones, take part before you promote, say you are the maker, make your thing easy to try, never ask for votes or use extra accounts, and stay for the conversation. Being welcome is slower than being loud, and it lasts far longer.