EarShots.dev
Open navigation

Replying to developers: community rules and disclosure

Developer communities set different rules for generated content, commercial promotion and affiliation disclosure. Check the policy for the specific channel, answer the technical question, and make your relationship to the product clear.

David ZeledonCEO, Founder of EarShots.Dev6 min readPublished Sources checked

Takeaways

Accuracy, moderation and authorship policies

Stack Overflow cited incorrect answers and moderation volume when it introduced its ChatGPT restriction. Other communities have their own policies; do not assume they share one rationale.

In December 2022 it temporarily banned answers generated by ChatGPT. It said the rate of correct answers was too low and the volume threatened its volunteer curation.[6] The concern has spread since. In the 2025 Stack Overflow survey, 46% of respondents said they distrust the accuracy of AI tools, against 33% who trust it.[7]

Community rules on generated content

Source: Community policies linked in the article.[1] Dates identify the cited policy or announcement, not a uniform enforcement timeline.

Check both content rules and authorship rules. A technically correct AI-edited comment can still violate a platform policy that prohibits AI-edited text.

What are the rules on each channel?

Check the current platform policy and any community-specific rules before drafting a reply.

Hacker News

Hacker News guidelines prohibit generated and AI-edited comments.[1] Write every comment yourself. Disclose your affiliation in the comment. Answer the technical question before you mention anything you sell.

Reddit, starting with r/programming

The moderators' April 1, 2026 announcement trialed a restriction on posts about LLMs for two to four weeks. It explicitly distinguished that topic restriction from the existing ban on LLM-generated text. On May 23, moderators ended the trial and made AI and LLM topics off-topic except for deeply technical implementation content.[2][3] Check the current subreddit policy before participating.

Stack Overflow

Stack Overflow's ban on ChatGPT-generated answers started in December 2022 and said it would act against people posting them.[6] Answers should be your own work, tested, and complete without a link. If you link your docs, put the working code in the answer too.

DEV

DEV allows AI-assisted articles if the author discloses AI use, fact-checks the content and can stand behind it.[4] Its AI-content policy prohibits generated comments, with exceptions for basic translation, grammar and assistive tools. AI-assisted articles must not promote a business. The backlink restriction also lists exceptions for personal blogs and company-blog posts shared under the company's DEV organization. Violations can lead to reduced visibility, suspension or a ban.

ChannelAI-written postsSelf-promotionWhat to do
Hacker NewsProhibited in comments[1]Read the guidelinesWrite it yourself, disclose, answer first
r/programmingGenerated text banned; AI topics restricted[3]Per subreddit rulesRead the sidebar, add real substance
Stack OverflowGenerated answers banned[6]Answer must stand alonePut tested code in the answer
DEVAllowed with disclosure; no bot comments[4]AI-assisted articles cannot promote a businessTeach, disclose, no sales posts

Do you have to disclose that you work there?

For US product endorsements, FTC guidance treats employment as a connection that may affect how readers evaluate the recommendation. Disclose that connection clearly when it would not otherwise be apparent.[5] The FTC explains that readers may see an individual endorsement without visiting the author's profile. Put the relevant disclosure in the endorsement itself rather than relying on a biography.[5]

For example, identify your role in plain language: "I work on the software development kit (SDK) team at Acme." Place the disclosure where readers will see it with the recommendation; adequacy depends on context.

Technical reply checklist

Start with the developer's problem and the evidence needed to solve it. Mention your product when it is relevant, and identify unsupported behavior or limitations explicitly.

  1. Read the whole thread. Understand what they tried and what failed.
  2. Disclose first. One line, at the top.
  3. Answer the actual question. Give the fix, the command or the config. Test it.
  4. Show your evidence. Link the exact doc section or the GitHub issue that confirms the behavior.
  5. Admit limits. If your product cannot do it, say so and suggest what can.
  6. Skip the pitch. No pricing, no demo links, no "DM me".
  7. Write it yourself. Research with any tool you like. The words in the comment should be yours, especially on Hacker News.
  8. Check the rules once more. Subreddit sidebar, Hacker News guidelines, DEV policy.

EarShots reply workflow

EarShots finds the threads and sorts them. On X, LinkedIn and Reddit it drafts a reply grounded in your docs for a person to review. It never posts for you.

A teammate reads the draft, rewrites it in their own words, adds their disclosure, and posts from the original thread. EarShots does not draft replies for Hacker News, Stack Overflow or DEV. There, it surfaces the thread and your team writes the reply from scratch.

FAQ

Can I use AI to draft replies on Hacker News?

Hacker News guidelines prohibit generated and AI-edited comments. Use research tools to find the facts, then write the comment yourself.

Do I have to say I work for the company when I reply?

For US endorsements, FTC guidance calls for disclosure of a material employment connection when it would not otherwise be apparent. Include it with the endorsement; a profile biography may not be seen by the reader.

Usually, when the link answers the question and the subreddit allows it. Check each subreddit's rules first, disclose your affiliation, and put the answer in the comment itself.

For where to find these conversations in the first place, read Where developers talk about your product in 2026. For the background on community bans, read Developer marketing in the age of AI.

Sources

  1. Hacker News Guidelines. Y Combinator.
  2. Announcement: Temporary LLM Content Ban. r/programming moderators, April 1, 2026.
  3. Announcement: We've Updated The Rules, and April Is Finally Over. r/programming moderators, May 23, 2026.
  4. Guidelines for AI-assisted Articles on DEV. DEV Community.
  5. The FTC's Endorsement Guides: What People Are Asking. Federal Trade Commission.
  6. Policy: Generative AI is banned. Meta Stack Overflow.
  7. 2025 Stack Overflow Developer Survey. Stack Overflow.

Last verified October 22, 2026.

Related guides

Industry Applications

Relevant Industries

Browse all industries →