← 行銷專欄 Marketing · 行銷學習地圖 W6-7
技術人發文平台：文化與禁忌
Tech Publishing Platforms: Culture & Taboos
每個平台的反 spam 免疫系統不同，但原理相同——社群先於促銷。學會各平台的語言，你的產品才有資格被看見。
Every platform has a different anti-spam immune system, but the principle is the same — community before promotion.
🎯 學完你能做到
🎯 Learning Goals
① 為產品規劃完整的 Show HN 貼文與 PH launch campaign ② 說出各平台的三大禁忌 ③ 設計 canonical URL 跨發策略 ④ 評估 build in public 的透明度取捨
① Plan a full Show HN post and PH launch campaign ② Name each platform's top taboos ③ Design a canonical URL cross-posting strategy ④ Weigh build-in-public transparency tradeoffs
標準 Launch 鏈路（大圖景）
The Standard Launch Chain
先看整條路，再學每一站
See the whole road before each stop
1. 自家 blog
canonical 源頭
canonical 源頭
→
2. dev.to / Hashnode
跨發吃分發
跨發吃分發
→
3. X build in public
日常蓄能
日常蓄能
→
4. GitHub README
landing page 就緒
landing page 就緒
→
5. HN / PH / Reddit
同窗口引爆
同窗口引爆
→
6. IH postmortem
回收長尾
回收長尾
- 共同禁忌（全平台通用）：假互動（vote ring / 買星 / 小號）、行銷語言、launch 日才開始行銷
- Universal taboos: fake engagement (vote rings / bought stars / sockpuppets), marketing speak, starting marketing on launch day
- 2025-26 三大變化：PH hunter 機制失效（self-hunt 成主流）、Reddit 官方 90/10 條文退役但 spam filter 更嚴、頭部 build in public 帳號收斂營收透明度
- Three 2025-26 shifts: PH hunters lost their edge (self-hunt is mainstream), Reddit's official 90/10 rule retired but spam filters tightened, top build-in-public accounts pulled back revenue transparency
Hacker News
求知好奇心是唯一貨幣 · 一句行銷話就出局
Intellectual curiosity is the only currency
📜 規則與文化Rules & Culture
- Show HN 硬門檻：必須可實際試用——landing page、waitlist、募資頁全部不合格；盡量不用註冊就能試
- Show HN hard requirement: must be tryable — landing pages, waitlists, crowdfunding pages don't qualify; ideally no sign-up needed
- 標題規則（官方）：不可全大寫、驚嘆號、自誇詞；有效標題＝事實陳述 + 引發技術好奇
- Title rules (official): no all-caps, exclamation points, superlatives; effective = factual + technically curious
- 帳號要像「人」：不用公司名、不叫朋友灌 booster comments（投票環偵測會懲罰）
- Be a person: no company-name accounts, no friend-boosted comments (vote-ring detection punishes)
- 回覆每一則留言含負評——創辦人在 thread 的態度被當作產品的一部分
- Reply to every comment, including negative ones — your thread demeanor is judged as part of the product
- 長期經營勝過單次 launch：每天一則基於實際經驗的冷靜留言
- Long-term presence beats one launch: one calm, experience-based comment per day compounds
絕對禁忌：vote ring（拉票互投）、行銷語言（"revolutionary"、"game-changing"）、公司帳號發文、短期重複提交。Absolute taboos: vote rings, marketing superlatives, company accounts, rapid resubmission.
案例：Case: 五年後二度 Show HN 才上首頁——改變在於加入創辦故事與 code examples、把框架從 launch 改成 lesson。launch day 帶來約 468 個 active users。A second Show HN five years later hit the front page — by adding the founding story and code examples, reframing from launch to lesson. ~468 active users on launch day. Postmortem ↗
Product Hunt
launch 是 campaign，不是 event · self-hunt 已是主流
A launch is a campaign, not an event · Self-hunt is mainstream
🚀 2025-26 機制現況 + 準備清單Current Mechanics + Prep List
- Hunter 機制已弱化：官方明講找第三方 hunter 無可見優勢；79% featured 是 self-hunted——自己 hunt 自己即可
- Hunters have lost their edge: officially no visible advantage; 79% of featured products are self-hunted
- 演算法重 engagement quality（留言深度）> 純 upvote；前 4 小時 velocity 權重極高
- Algorithm favors engagement quality (comment depth) over raw upvotes; first-4-hour velocity is critical
- 時間：12:01 AM PT 開跑吃滿 24 小時；週二至四流量大競爭烈、週末門檻低曝光少
- Timing: start at 12:01 AM PT for the full 24h; Tue-Thu = high traffic & competition, weekends = lower bar & exposure
- 1提前 30 天上 Coming Soon 頁蓄積 followers（launch 日收 email 通知）30 days out: Coming Soon page to accumulate followers
- 2準備短影片（#1 得主幾乎都有）+ 預寫 maker's first comment（70% 冠軍有）Prepare a short video + pre-write the maker's first comment
- 3Launch day：15 分鐘內回覆每則留言；請人「留 thoughtful feedback」而非「幫我 upvote」（直接討票違規）Launch day: reply within 15 min; ask for "thoughtful feedback," never upvotes (against rules)
- 4會後 nurture：感謝、回訪、把留言者轉化為早期用戶Post-launch nurture: thank, follow up, convert commenters to early users
常見失敗：launch 早上才開始行銷、產品與 PH 社群不對頻、頁面 3 秒看不懂、沒影片、選錯日子。Common failures: marketing starts on launch morning, product-community mismatch, page unclear in 3 seconds, no video, wrong day.
案例：Case: 分階段社群動員與時區規劃，連續 3 天守住 Top 5。Staged community mobilization + timezone planning held Top 5 for 3 straight days. Mind the Product ↗
Reddit
每個 subreddit 是獨立國家 · journey post 勝過產品介紹
Every subreddit is its own country · Journey posts beat product intros
🗺️ 生存規則Survival Rules
- 9:1 rule 現況：官方 90/10 wiki 已下架，改為「genuine participant」原則性判斷；但 spam filter 實務仍看 promotional ratio，老手採 95:5
- 9:1 rule today: the official 90/10 wiki is retired, replaced by "genuine participant" judgment; spam filters still measure promotional ratio — veterans use 95:5
- 促銷友善區：r/SideProject（30 萬+）、r/EntrepreneurRideAlong（journey 敘事）、r/somethingimade（自製作品）；r/InternetIsBeautiful 不允許需註冊的產品；發文前必讀 sidebar rules
- Promo-friendly: r/SideProject (300K+), r/EntrepreneurRideAlong, r/somethingimade; r/InternetIsBeautiful bans sign-up-required products; always read sidebar rules
- Shadowban 機制：短時間跨 sub 貼同連結、低 karma 帶連結、高促銷比例 → 貼文只有自己看得到；用 logged-out 視窗自檢
- Shadowbans: same link across subs quickly, low-karma link posts, high promo ratio → your posts become invisible; self-check in a logged-out window
- 成功格式：誠實 journey post（「做了 X、學到 Y、搞砸了 Z」）>> 產品介紹；留言區才是主戰場（利益揭露前提下答題帶工具）
- Winning format: honest journey posts ("built X, learned Y, botched Z") >> product intros; comments are the real battlefield (answer questions, disclose affiliation)
- 新帳號先 2-4 週純參與累積 karma 再促銷
- New accounts: 2-4 weeks of pure participation before any promotion
絕對禁忌：多帳號互推（永 ban）、同連結轟炸多個 sub、假裝路人推自家產品（被 mod 公開處刑）。Absolute taboos: multi-account promotion (permanent ban), link-bombing subs, astroturfing your own product (public mod shaming).
dev.to / Hashnode / Medium
Canonical URL 是跨發策略的命脈
Canonical URLs are the lifeline of cross-posting
🔗 跨發策略Cross-posting Strategy
自家 blog 先發
SEO 權重歸自己
SEO 權重歸自己
Own blog first
SEO credit stays home
SEO credit stays home
→
dev.to
canonical_url
canonical_url
→
Hashnode
originalArticleURL
originalArticleURL
→
Medium
canonical link
canonical link
- 不設 canonical 的代價：Google 會把平台版本排在你的原站之上
- Without canonical: Google ranks the platform copy above your own site
- dev.to 設定：Rich editor 齒輪填 Canonical URL；markdown editor 在 front matter 加
canonical_url: - dev.to: gear icon in rich editor, or
canonical_url:in markdown front matter - 內容公式：技術含量是主菜、產品是配菜——「How I built X」與踩坑文表現最好；含 code snippets 與 diagrams 的文互動率是純文字 2 倍（Hashnode 數據）
- Content formula: tech substance is the main course, product is the side — "How I built X" and pitfall posts win; code + diagrams get 2x engagement (Hashnode data)
- Medium 2025-26：Partner Program 連續改版（獎勵帶新流量的作者）；社群共識＝當分發管道可以、當收入來源不行；AI 量產文無法進分潤
- Medium 2025-26: Partner Program repeatedly revamped; consensus = fine as distribution, not as income; AI-mass-produced posts are excluded from payouts
案例：Case: Draft.dev 客戶技術文登上 HN，單日 5 個 demo requests；referral 流量數週內成長 3 倍。A Draft.dev client's technical post hit HN: 5 demo requests in one day; referral traffic tripled within weeks. Case studies ↗
Substack
有內建成長迴路的社交網路 · 40% 新訂閱來自站內
A social network with built-in growth loops · 40% of new subs come from within
📈 成長引擎Growth Engines
- Recommendation network 是最強迴路：主動推薦別人的作者被回推機率 3 倍；實作＝找 10-15 個規模相近、主題互補的刊，先讀對方最近三期再私訊提互推
- Recommendations are the strongest loop: authors who recommend others are 3x more likely to be recommended back; find 10-15 similar-size complementary newsletters
- Notes = 平台內 Twitter：有創作者 70% 新訂閱來自 Notes（每天 20-30 分鐘）
- Notes = in-platform Twitter: some creators get 70% of new subs from Notes (20-30 min/day)
- 免費訂閱者先行：paid conversion 跟著 free list 成長走，不要太早鎖 paywall
- Free subscribers first: paid conversion follows free list growth; don't paywall too early
- CTA 工程：文內、email header/footer 放 subscribe/share 鈕；Substack 連結進所有 social bio 與 email 簽名檔
- CTA engineering: subscribe/share buttons in-post and in email header/footer; link in every bio and signature
案例：Case: Amy Suto 公開拆解把個人品牌 Substack 經營到 $180,000+ ARR 的過程。Amy Suto's public breakdown of growing her Substack to $180,000+ ARR. amysuto.com ↗
Build in Public (Indie Hackers + X)
透明度是貨幣，但 radical transparency 正在退潮
Transparency is currency, but radical transparency is receding
🔄 模式與轉折Patterns & the Shift
- IH 的貨幣是 transparency：$1K MRR 是最受重視門檻；附 timeline + channel breakdown + lessons 的 milestone 文互動是純數字的 3-5 倍
- IH's currency is transparency: $1K MRR is the most celebrated milestone; posts with timeline + channel breakdown + lessons get 3-5x engagement
- Marc Lou 公式（170K followers）：「1. Launch tiny startups 2. Share results 3. Repeat」
- Marc Lou's formula (170K followers): "1. Launch tiny startups 2. Share results 3. Repeat"
- 賣鏟子策略：build in public 的終局常是「教別人 build」本身變成產品（ShipFast 等）
- Selling shovels: the endgame is often "teaching others to build" becoming the product (ShipFast etc.)
- 內容門檻：對不是你的人也有趣才有傳播力——數據截圖、決策思路、失敗自嘲 >> 流水帳進度
- Content bar: must interest strangers — data screenshots, decision reasoning, failure humor >> progress logs
- 鐵三角：X 養受眾 → PH/HN launch 收割 → IH 深度 postmortem 回流
- The triangle: X builds audience → PH/HN launches harvest → IH postmortems recycle
2025-26 轉折：頭部 indie hackers（levelsio、Danny Postma 等）已停止公開營收——安全風險與抄襲者是主因。「radical transparency」退潮，轉向「selective transparency」。分享營收前先權衡。2025-26 shift: top indie hackers (levelsio, Danny Postma…) stopped sharing revenue — security and copycats. Radical transparency is giving way to selective transparency. Weigh before you share.
GitHub
README = landing page · 四套獨立 discovery 機制
README = landing page · Four independent discovery systems
⭐ 四套機制與槓桿Mechanics & Levers
| Discovery | 排序邏輯 | Ranking Logic |
|---|---|---|
| Trending | star velocity（星數/時間）——集中一天引爆比分散累積有效 | Star velocity — concentrated bursts beat slow accumulation |
| Topics | tag 策略 | Tag strategy |
| Search | README 內容 + star 總數 | README content + total stars |
| Explore | 個人化訊號 | Personalization signals |
- README = landing page：demo GIF、quick start、badges、清楚 value prop——轉換效率是簡陋 README 的 3-5 倍
- README = landing page: demo GIF, quick start, badges, clear value prop — 3-5x conversion vs a bare README
- Awesome lists 潛規則：請朋友或早期用戶代為提交 PR——很多 maintainer 拒收自薦、歡迎第三方推薦
- Awesome list etiquette: have a friend or early user submit the PR — many maintainers reject self-nominations but welcome third-party ones
禁忌：買星、star-for-star 互刷——GitHub 會清除，且開發者受眾抓包後信譽歸零。Taboos: bought stars, star-for-star schemes — GitHub purges them, and dev audiences never forgive fakes.
案例：Case: 一週內 3,500+ GitHub stars 的完整實戰（README 優化 + 分發時機協同）。3,500+ stars in one week (README optimization + coordinated distribution timing). freeCodeCamp ↗
實作練習
Practice Exercises
用捕夢網生成器當 launch 素材
Use the dreamcatcher generator as launch material
練習 1（W6）：Show HN 草稿
Exercise 1 (W6): Show HN Draft
為捕夢網生成器寫 Show HN 草稿：標題（事實陳述+技術好奇，聚焦 canvas 生成演算法或 SVG 雷切輸出）+ first comment（創辦故事、技術決策、已知限制）。對照官方 guidelines 自檢。
Draft a Show HN for the dreamcatcher generator: title (factual + technically curious) + first comment (founding story, technical decisions, known limitations). Self-check against official guidelines.
練習 2（W6）：PH launch 30 天計畫
Exercise 2 (W6): 30-Day PH Launch Plan
列出 launch 前 30 天的週計畫表：Coming Soon 頁、影片腳本、maker's first comment 草稿、launch day 時間表（誰在哪個時段顧留言）。
Draft the 30-day plan: Coming Soon page, video script, maker's first comment, launch-day hour-by-hour schedule.
練習 3（W7）：README 重寫 + canonical 跨發鏈
Exercise 3 (W7): README Rewrite + Canonical Chain
①把 dreamcatcher repo 的 README 依 landing page 標準重寫大綱（demo GIF、quick start、SVG 雷切賣點）。②設計跨發鏈：mattye.dev 文章 → dev.to → Medium，標出每站 canonical 設定位置。
① Outline a landing-page-grade README for the dreamcatcher repo. ② Design the cross-post chain: mattye.dev → dev.to → Medium, marking each canonical setting.