Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

What I Learned from 3 Months of Organic Firefox Extension Growth

Description and use

The author shows how organic growth of Firefox extension users can be achieved through Mastodon and Dev.to posts, while other platforms proved ineffective due to account and IP restrictions.

Problem

How to grow Firefox extension users organically without paid advertising.

Outcome

Organic growth via Mastodon and Dev.to produced modest but measurable increases in ADU, while attempts on HN, Reddit, Lemmy, BetaList, SaaSHub, and Product Hunt were ineffective due to platform restrictions or low account reputation.

Workflow

  • Publish extensions on AMO
  • Track ADU via AMO metrics
  • Post content on Mastodon using relevant hashtags (#Firefox, #Privacy, #OpenSource, #FOSS)
  • Write Dev.to articles targeting "Firefox extensions" and "new tab productivity" queries
  • Attempt posts on HN "Show HN" (failed due to low karma)
  • Attempt posts on Reddit (failed due to IP block)
  • Evaluate other directories (Lemmy, BetaList, SaaSHub, Product Hunt) and note limitations

Evidence

Mastodon: The Fediverse audience skews toward FOSS users and developers who are already Firefox users. Posting genuine content (not spam) in relevant hashtags (#Firefox, #Privacy, #OpenSource, #FOSS) drives measurable engagement and eventual installs.

Source

Dev.to articles: Slow-burn SEO. Articles ranking for "Firefox extensions" or "new tab productivity" queries drive occasional installs. Not high volume, but persistent.

Source

HN "Show HN": Attempted, but new HN accounts with 1 karma get posts marked <code>[dead]</code> automatically. The value here is near-zero for new accounts.

Source

Reddit: IP-blocked from server. Low karma account gets posts removed. High potential if executed from a home browser with karma.

Source

Lemmy: Account got banned after too many posts (spam detection). New applications denied.

Source

  • Record date: 2026-10-26T00:26:43.747Z