Mozilla is eliminating its advocacy division

Original Article ↗ Hacker News Discussion ↗

Mozilla’s structure and the advocacy layoffs

  • Commenters clarify that the 30% cut applies to Mozilla Foundation staff (120 people), not Mozilla Corporation (~1,000), so browser development staff are mostly separate.
  • Some speculate the cuts anticipate declining Google search revenue and regulatory pressure, but this is framed as conjecture.
  • Others question how much money is really saved compared to Mozilla’s other spending.

Strategy, leadership, and missed opportunities

  • Strong criticism of “obscene” executive pay, US cost structure, and spending on side projects (Pocket, AI efforts, ads) instead of core browser work or a financial endowment.
  • Several argue Mozilla drifted into idealistic or “activist” projects, with weak commercial strategy and no coherent way to pay the bills.
  • Others push back, noting that not all “advocacy” is fluff; MDN and Rust are cited as substantial contributions, though Rust’s later success is debated as “no longer Mozilla’s.”

Effectiveness and value of advocacy

  • One view: advocacy failed—Firefox share collapsed, web centralization grew, and privacy and openness allegedly worsened.
  • Counterview: Mozilla was key to wins like HTTPS-by-default via Let’s Encrypt and standards work; failures reflect broader industry dynamics, not just Mozilla.
  • Some argue Mozilla should focus almost solely on “the best browser imaginable”; others say exploratory side projects are necessary to avoid being blindsided by shifts (e.g., mobile).

Browser monoculture, alternatives, and funding

  • Widespread concern about a de facto Chrome/Blink monoculture and Google’s conflicts of interest (ads vs. users, Manifest V3, ad blocking).
  • Suggested responses:
    • New lean org in a cheaper country forking Firefox.
    • Government/EU- or LATAM-funded fork, though skeptics question cost, complexity, and political will.
    • Existing forks (LibreWolf, Zen, Pale Moon, etc.) and new projects (Ladybird, Servo) are mentioned, but maintenance burden and sustainability are questioned.
  • Some note that many “independent” browsers (Opera, Falkon, Orion, etc.) rely on Chromium/WebKit, so they don’t solve engine-level dependence on big tech.

Firefox product experience and ecosystem pressures

  • Some users say Firefox “works great”; others complain about neglected UX issues (e.g., address bar sizing) and slow response to long-standing bugs.
  • Reports of feature blocking (e.g., Slack Huddles) and user-agent checks illustrate how a minority browser can face reduced functionality.
  • Several see Google’s role as main funder as a structural conflict that undermines true independence.