Posting Guidelines
Clear evidence and respectful collaboration make technical answers easier to trust.
Ask one specific question
Use a title that names the technology and observable behavior. Explain what you expected, what actually happened, and the smallest steps another person can follow.
Include useful environment details
Share relevant language, framework, dependency, runtime, browser, platform, and version information. Say what you already tried and whether production is affected. Use “Not sure” instead of guessing.
Publish only what you may share
Never post passwords, API keys, tokens, private customer data, internal URLs, proprietary code without permission, or credentials disguised as examples. Reduce code to a minimal authorized sample.
Handle security concerns privately
Choose Security Concern. New security-sensitive reports begin as Private Diagnostics and go to the restricted review path—not the public feed.
Make answers verifiable
Explain the reasoning, assumptions, version context, expected side effects, test steps, and rollback when relevant. Highest-voted does not mean automatically correct.
Label AI assistance honestly
Review AI-generated material before sharing it. Genesis output is labeled “AI-generated diagnostic — verify before applying” and may never impersonate a human author.
Avoid duplicates and noise
Search exact error text first. Improve an existing question when it covers the same problem. Do not post ads, referral spam, repeated promotional links, or engagement bait.
Share responsibly
Public threads may be shared by deliberate user action. Unlisted, private, draft, quarantined, or security-sensitive content must not be redistributed.