No AI* Here – A Response to Mozilla's Next Chapter

Original Article ↗ Hacker News Discussion ↗

Reactions to Mozilla’s AI Plans

  • Many see the backlash as less “anti‑AI” and more “anti‑Mozilla‑strategy”: fear that yet another fad (AI) will consume resources instead of fixing core browser issues.
  • Some argue AI integration is inevitable for non-technical users who now equate “AI box” with “better browsing,” so Mozilla has to follow for positioning and revenue.
  • Others counter that Firefox’s only viable niche is power users who explicitly don’t want forced AI and value control, privacy, and minimalism.

Local vs Cloud Models and Technical Feasibility

  • Strong support for local, narrowly scoped models (e.g., translation, page summarization) that don’t exfiltrate data.
  • Skepticism that local LLMs on “average” hardware can support ambitious “agentic browsing” anytime soon, despite future NPUs/Apple/AMD advances.
  • Concern that local models will be deliberately underpowered to push users toward paid cloud integrations.

Privacy, Data, and Monetization

  • Deep distrust of Mozilla’s updated privacy policy and the removal of “never sell personal data” language; some see this as groundwork for AI/ads-based monetization.
  • Worry that browser-level AI, especially cloud-based, will leak sensitive work/creative data and be used to train models that automate those same jobs.
  • Some say technical “black box” arguments are overstated; what matters is where the model runs and what data it can send out.

UX, Defaults, and Configuration

  • Complaints about recent Firefox AI features: sidebars, context-menu items, AI tab grouping (“uses AI to read your open tabs”) seen as intrusive and poorly designed.
  • Disabling via about:config or enterprise policies is viewed as unrealistic for most users and fragile (options move, break, or are re-enabled over upgrades).
  • Broader frustration that each fresh install requires turning off more “annoyances,” and that defaults increasingly prioritize monetization/experiments over users.

Philosophy: What a Browser Should Be

  • One camp: browser = user agent / “HTML viewer + extensions”; AI belongs in separate apps or optional extensions, not “the heart of the browser.”
  • Another camp: AI is just another tool like translation or spellcheck; embedding summarization, search-on-page, and form-filling could genuinely help, if strictly opt‑in.

Waterfox and Alternatives

  • Waterfox’s “no AI, ever (for now)” positioning is welcomed as a rare “no‑AI” option and a refuge from AI‑everywhere pressure.
  • Some note Waterfox (and other forks) depend on Mozilla’s engine; if Firefox fails, these forks are at risk too.
  • Others say they’ll simply move again if needed; they value current non‑AI behavior over trying to “save” Firefox as an institution.