hacker-news-strategy

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Hacker News Strategy

Hacker News运营策略

Hacker News is the most influential developer community — and the easiest to get wrong. This skill covers what actually works, what gets you flagged, and how to build authentic presence.

Hacker News是最具影响力的开发者社区——但也是最容易运营出错的社区。本技能涵盖了真正有效的方法、会导致内容被标记的行为，以及如何建立真实的社区存在感。

Before You Start

开始之前

Read
```
.agents/developer-audience-context.md
```
if it exists
Check if the product/content is genuinely interesting to HN's audience (hackers, founders, deep tech enthusiasts)
Be honest: HN users can smell marketing from miles away

如果存在
```
.agents/developer-audience-context.md
```
文件，请先阅读
确认产品/内容对HN受众（黑客、创始人、深度技术爱好者）确实有吸引力
保持真诚：HN用户能轻易识破营销话术

Understanding HN's Culture

理解HN的社区文化

Who's Actually on Hacker News

Hacker News的核心用户群体

Segment	What they care about
Founders	Fundraising, growth tactics, startup war stories
Senior engineers	Deep technical content, architecture, systems
Tech leads	Engineering management, team scaling, processes
Indie hackers	Solo projects, bootstrapping, revenue
Researchers	AI/ML, distributed systems, PLT, security

用户群体	关注重点
创始人	融资、增长策略、创业故事
资深工程师	深度技术内容、架构设计、系统搭建
技术负责人	工程管理、团队扩张、流程优化
独立开发者	个人项目、自启动创业、营收模式
研究人员	AI/ML、分布式系统、编程语言理论（PLT）、安全领域

What HN Values

HN推崇的价值观

Technical depth over marketing polish
Genuine novelty over incremental updates
Transparency over corporate speak
Building in public over stealth launches
Contrarian insights over conventional wisdom

技术深度优先，而非营销包装
真正的创新优先，而非增量更新
透明真诚优先，而非官方话术
公开构建优先，而非隐秘发布
逆向洞察优先，而非传统共识

What HN Hates

HN反感的内容

Self-promotion disguised as content
Clickbait headlines
Corporate PR speak
Engagement bait ("What do you think?")
Anything that feels like an ad

伪装成内容的自我推广
标题党
企业公关话术
互动诱饵（比如“你怎么看？”）
任何类似广告的内容

Post Types and When to Use Them

发布类型及适用场景

Show HN

Use when: You built something and want feedback from the community.

Requirement	Details
Must be something people can try	Live demo, downloadable, or detailed walkthrough
Must be new	Not a repost or minor update
Creator must be available	Answer questions in comments for 2-3 hours
Title format	"Show HN: [Name] – [One-line description]"

Good Show HN examples:

"Show HN: I built a SQLite extension for vector search"
"Show HN: Open source Heroku alternative written in Rust"
"Show HN: Real-time collaborative code editor in the browser"

Bad Show HN examples:

"Show HN: My startup just raised $5M" (not something to try)
"Show HN: We updated our pricing page" (not interesting)
"Show HN: Check out our new feature" (too vague)

适用场景：你开发了某个产品，希望获得社区反馈。

要求	细节
必须是可体验的内容	提供在线演示、可下载资源或详细操作指南
必须是全新内容	不能是重复发布或小版本更新
创建者必须在线	在发布后的2-3小时内回复评论中的问题
标题格式	"Show HN: [名称] – [一句话描述]"

优质Show HN示例:

"Show HN: I built a SQLite extension for vector search"
"Show HN: Open source Heroku alternative written in Rust"
"Show HN: Real-time collaborative code editor in the browser"

糟糕Show HN示例:

"Show HN: My startup just raised $5M"（无体验内容）
"Show HN: We updated our pricing page"（缺乏吸引力）
"Show HN: Check out our new feature"（描述模糊）

Launch HN

Use when: Major company launch or significant funding announcement.

Guideline	Details
Include technical details	What's under the hood, architectural decisions
Share the journey	How you got here, lessons learned
Be available	Founders should answer questions personally
Avoid PR speak	Write like a human, not a press release

适用场景：公司重大发布或重要融资公告。

指南	细节
包含技术细节	底层实现、架构决策
分享创业历程	发展过程、经验教训
创始人亲自在线	创始人需亲自回复问题
避免公关话术	用普通人的语气写作，而非新闻稿风格

Regular Submissions

常规发布

Use when: Sharing interesting content (yours or others).

What works	What doesn't
Technical blog posts with depth	Listicles and "10 tips" posts
War stories with lessons	Company announcements
Deep dives into problems	Product updates
Original research or data	Repackaged content
Contrarian technical takes	Obvious or consensus opinions

适用场景：分享有趣的内容（自己或他人的）。

有效内容	无效内容
有深度的技术博客文章	清单类或“10个技巧”类文章
带有经验教训的实战故事	公司公告
问题深度剖析	产品更新通知
原创研究或数据	二次包装的内容
逆向技术观点	显而易见或达成共识的观点

Title Optimization

标题优化

Title Principles

标题原则

Do	Don't
Be specific and concrete	Use vague buzzwords
State what it is, not why it's great	Include superlatives ("amazing," "best")
Use technical terms appropriately	Dumb down for broader appeal
Keep it factual	Use clickbait patterns

应该做	不应该做
具体、明确	使用模糊的流行术语
说明内容是什么，而非有多好	使用最高级词汇（比如“惊人的”、“最佳的”）
合理使用技术术语	为了扩大受众而简化内容
保持客观真实	使用标题党格式

Title Transformations

标题优化示例

Before (bad)	After (good)
"The Best Way to Handle Errors in Node.js"	"Error handling patterns in Node.js production systems"
"We Made Deployments 10x Faster"	"How we reduced deployment time from 20min to 2min"
"Announcing Our Amazing New Feature"	"Show HN: [Feature] – [What it does]"
"You Won't Believe What We Found"	"[Specific finding] in [specific context]"
"Why Everyone Should Use TypeScript"	"TypeScript's type system caught 15% of our production bugs"

优化前（糟糕）	优化后（优质）
"The Best Way to Handle Errors in Node.js"	"Error handling patterns in Node.js production systems"
"We Made Deployments 10x Faster"	"How we reduced deployment time from 20min to 2min"
"Announcing Our Amazing New Feature"	"Show HN: [Feature] – [What it does]"
"You Won't Believe What We Found"	"[Specific finding] in [specific context]"
"Why Everyone Should Use TypeScript"	"TypeScript's type system caught 15% of our production bugs"

HN Moderators Edit Titles

HN管理员会修改标题

Be aware: HN moderators (especially dang) will edit sensationalized titles to be more neutral. They'll also merge duplicate submissions and sometimes give worthy posts a second chance.

请注意：HN管理员（尤其是dang）会将耸人听闻的标题修改得更中立。他们还会合并重复发布的内容，有时也会给优质内容第二次曝光机会。

Timing and Mechanics

发布时机与机制

Best Posting Times

最佳发布时间（太平洋时间）

Time (PT)	Why it works
6-9 AM	Catches US East Coast morning, Europe afternoon
10 AM - 12 PM	Peak US activity
Avoid: Weekends	Lower traffic, but less competition

时间	优势
6-9 AM	覆盖美国东海岸早晨、欧洲下午时段的用户
10 AM - 12 PM	美国用户活跃峰值
避免：周末	流量较低，但竞争也更少

The Algorithm

排名算法

Initial upvotes in first 1-2 hours matter most
Comments boost ranking (engagement signal)
Fast upvotes can trigger the "flamewar detector" penalty
Posts from new accounts get extra scrutiny
Controversial posts get rank penalties

发布后1-2小时内的初始点赞量最为关键
评论会提升排名（互动信号）
快速获得大量点赞可能触发“论战检测器”惩罚
新账号发布的内容会受到额外审核
争议性内容会被降权

What Kills Posts

导致内容“夭折”的原因

Killer	Why
Voting rings	Multiple accounts/friends upvoting = detected and penalized
No early engagement	Post dies without initial momentum
Flagged by users	Multiple flags = post hidden
Duplicate content	Already posted = merged or killed
Self-promotion pattern	Multiple posts about same company

因素	原因
刷赞团伙	多个账号/好友刷赞会被检测并惩罚
早期无互动	没有初始热度的内容会逐渐沉没
用户标记	多次被标记的内容会被隐藏
重复内容	已发布过的内容会被合并或下架
自我推广模式	多次发布同一公司的相关内容

Comment Strategy

评论策略

If It's Your Post

针对自己的发布内容

Timing	Action
Immediately	Post a top-level comment with context, backstory, or technical details
First 2 hours	Respond to every comment, especially critical ones
Throughout day	Keep checking back, answer follow-ups

Your first comment template:

Hey HN, [your name] here, [role] at [company/project].

Quick backstory: [1-2 sentences on why you built this]

Technical context: [What's interesting under the hood]

Happy to answer any questions about [specific technical areas].

时机	行动
发布后立即	发布一条顶级评论，提供背景、故事或技术细节
发布后前2小时	回复所有评论，尤其是批评性评论
全天	持续查看，回复后续问题

首条评论模板:

Hey HN, [你的名字]，我是[公司/项目]的[职位]。

简短背景：[1-2句话说明开发初衷]

技术细节：[底层有趣的实现点]

欢迎提问关于[具体技术领域]的任何问题。

Responding to Criticism

回应批评

Criticism type	Response strategy
Valid technical concern	Acknowledge, explain reasoning, ask for suggestions
Misunderstanding	Clarify without being defensive
Trolling	Don't engage, or one brief factual response
Feature request	"Good idea, I'll look into it" or explain constraints
Competitive comparison	Be gracious, focus on your approach

Never do:

Get defensive or sarcastic
Argue with critics
Dismiss valid concerns
Use corporate speak in responses

批评类型	回应策略
合理的技术质疑	认可问题，解释决策逻辑，征求建议
误解	澄清问题，避免防御性语气
恶意挑衅	不回应，或仅给出一次事实性回复
功能请求	“好主意，我会研究”或说明限制条件
竞品对比	保持谦逊，聚焦自身方案

绝对不要做:

防御或讽刺
与批评者争论
忽视合理质疑
用官方话术回应

Commenting on Others' Posts

在他人的发布内容下评论

Building karma through genuine participation:

Do	Don't
Share relevant technical experience	Promote your stuff in others' threads
Ask thoughtful questions	Leave generic praise
Add context from your expertise	Be contrarian just for attention
Correct misinformation politely	Start arguments

通过真诚互动积累社区声望（Karma）:

应该做	不应该做
分享相关技术经验	在他人的讨论中推广自己的内容
提出有深度的问题	留下泛泛的赞美
结合自身专业知识补充背景	为了博眼球而唱反调
礼貌纠正错误信息	引发争论

What Gets Flagged/Killed

会被标记/下架的内容

Automatic Red Flags

自动触发的风险行为

Behavior	Consequence
Asking for upvotes (anywhere)	Post killed, possible ban
Voting from same IP/network	Votes nullified, accounts penalized
Multiple accounts upvoting	Accounts banned
Submitting competitors negatively	Flagged as abuse
Astroturfing in comments	Account banned

行为	后果
求赞（任何渠道）	内容被下架，可能被封号
同一IP/网络投票	点赞被作废，账号受惩罚
多个账号刷赞	账号被封禁
恶意发布竞品负面内容	被标记为滥用行为
用虚假账号刷评论	账号被封禁

Content That Gets Flagged

会被标记的内容类型

Content type	Why it's flagged
Obvious marketing	Community polices this aggressively
Political hot takes	Off-topic for HN
Crypto/Web3 (often)	Community fatigue
Paywalled content	Frustrates readers
Low-effort content	Doesn't meet quality bar

内容类型	被标记原因
明显的营销内容	社区会严格监管此类内容
政治热点观点	不符合HN的讨论主题
加密货币/Web3内容（通常）	社区对此类内容已疲劳
付费墙内容	惹恼读者
低质量内容	不符合平台质量标准

Recovering from a Failed Post

内容“夭折”后的补救

Wait at least 24 hours before reposting
Change the title to be more specific/interesting
Add more context if it was unclear
Email the mods (hn@ycombinator.com) if you think it was unfairly killed
Consider: Maybe HN isn't the right audience for this

至少等待24小时再重新发布
修改标题，使其更具体/有吸引力
补充更多背景信息（如果之前内容模糊）
联系管理员（hn@ycombinator.com），如果你认为内容被误删
反思：也许HN不是该内容的合适受众

Building Karma Authentically

真实积累社区声望（Karma）

The Long Game

长期策略

Timeframe	Strategy
Week 1-4	Comment only. No submissions. Build karma through genuine engagement.
Month 2-3	Submit interesting content (not your own). Show you're a contributor.
Month 3+	Occasional submissions of your own work, mixed with other contributions.

时间段	策略
第1-4周	仅评论，不发布内容。通过真诚互动积累Karma。
第2-3个月	发布有趣的第三方内容，证明你是社区贡献者。
第3个月后	偶尔发布自己的作品，同时持续贡献其他内容。

Karma-Building Comments

高Karma评论模式

High-karma comment patterns:

Add context: "I worked on a similar system at [company], and we found..."
Share data: "Our benchmarks showed X when we tested this approach"
Provide alternatives: "Another option is Y, which works well when..."
Historical context: "This is similar to how Z solved this in the 90s"

补充背景：“我曾在[公司]做过类似系统，我们发现...”
分享数据：“我们的基准测试显示，使用这种方法时结果为X”
提供替代方案：“另一种选择是Y，在...场景下表现很好”
历史背景：“这和90年代Z解决该问题的方式类似”

What Karma Gets You

Karma的作用

Karma level	Benefit
30+	Can downvote comments
500+	Posts get more initial trust
1000+	Strong signal of genuine community member

Karma等级	权益
30+	可以给评论点踩
500+	发布的内容会获得更多初始信任
1000+	证明你是真实的社区核心成员

Platform-Specific Do's and Don'ts

平台专属注意事项

Do's

应该做

Do write like a human, not a company
Do share technical details generously
Do acknowledge limitations and trade-offs
Do respond to criticism gracefully
Do share your Show HN link with your team (for awareness, not coordinated upvoting)
Do participate in discussions even when not promoting
Do read HN daily to understand the culture

用普通人的语气写作，而非企业话术
慷慨分享技术细节
承认局限性和权衡取舍
优雅回应批评
和团队分享你的Show HN链接（仅用于告知，而非协调刷赞）
即使不推广内容，也参与社区讨论
每天阅读HN，了解社区文化

Don'ts

不应该做

Don't ask anyone to upvote (bannable offense)
Don't post the same thing repeatedly
Don't use clickbait titles
Don't be defensive in comments
Don't ignore criticism
Don't astroturf with fake accounts
Don't treat HN as a free marketing channel

不要请求任何人点赞（会被封号）
不要重复发布同一内容
不要使用标题党
不要在评论中防御
不要忽视批评
不要用虚假账号刷评论
不要把HN当成免费营销渠道

Tools

工具推荐

Tool	Use case
Octolens	Monitor HN for mentions of your product, competitors, and relevant keywords. Get alerts when discussions happen so you can participate authentically.
HN Search (hn.algolia.com)	Research past posts on your topic, see what worked
HN Front Page Check	Monitor if your post is on front page and at what rank
HN user pages	Research commenters before responding

工具	使用场景
Octolens	监控HN中提及你的产品、竞品及相关关键词的内容。当相关讨论出现时收到提醒，以便你真诚参与。
HN Search (hn.algolia.com)	研究同主题的过往发布内容，了解哪些方法有效
HN Front Page Check	监控你的内容是否登上首页及排名情况
HN用户主页	在回复前研究评论者背景

hacker-news-strategy

Original

Translation

Hacker News Strategy

Hacker News运营策略

Before You Start

开始之前

Understanding HN's Culture

理解HN的社区文化

Who's Actually on Hacker News

Hacker News的核心用户群体

What HN Values

HN推崇的价值观

What HN Hates

HN反感的内容

Post Types and When to Use Them

发布类型及适用场景

Show HN

Show HN

Launch HN

Launch HN

Regular Submissions

常规发布

Title Optimization

标题优化

Title Principles

标题原则

Title Transformations

标题优化示例

HN Moderators Edit Titles

HN管理员会修改标题

Timing and Mechanics

发布时机与机制

Best Posting Times

最佳发布时间（太平洋时间）

The Algorithm

排名算法

What Kills Posts

导致内容“夭折”的原因

Comment Strategy

评论策略

If It's Your Post

针对自己的发布内容

Responding to Criticism

回应批评

Commenting on Others' Posts

在他人的发布内容下评论

What Gets Flagged/Killed

会被标记/下架的内容

Automatic Red Flags

自动触发的风险行为

Content That Gets Flagged

会被标记的内容类型

Recovering from a Failed Post

内容“夭折”后的补救

Building Karma Authentically

真实积累社区声望（Karma）

The Long Game

长期策略

Karma-Building Comments

高Karma评论模式

What Karma Gets You

Karma的作用

Platform-Specific Do's and Don'ts

平台专属注意事项

Do's

应该做

Don'ts

不应该做

Tools

工具推荐

Show HN Launch Checklist

Show HN发布检查清单

Related Skills

相关技能