Orbit by Mozilla

Overview of Orbit

  • Firefox add‑on that summarizes and answers questions about current page content (articles, emails, YouTube, etc.).
  • Uses a cloud‑hosted Mistral 7B model on Mozilla’s Google Cloud Platform (GCP) instance.
  • Free to use; no account required; FAQ says user data isn’t used for training and model can be swapped later.

AI Model, Hosting, and Cost

  • Many find Mistral 7B underwhelming: small, older model, limited vs newer 7–8B options.
  • Some note 7B can work well in production when used within careful systems (e.g., RAG, human‑in‑the‑loop).
  • Widespread skepticism about sustainability: GPUs and hosting are expensive; unclear how Mozilla will pay long‑term.
  • One commenter points out Fakespot involvement and speculates ads may be the eventual monetization.

Privacy and Data Trust

  • Strong pushback on “AI you can trust” marketing.
  • Concerns that all page content (including emails, documents) is sent to Mozilla’s servers on GCP.
  • Debate over whether GCP itself is safe: some argue Google cannot risk abusing customer data; others distrust all cloud providers and note Mozilla’s mixed privacy record (telemetry, past experiments, ad partnerships).
  • Some see this as contradicting Mozilla’s “privacy‑first” branding.

UX and Product Design Feedback

  • Major complaint: a permanent floating orb on pages; many uninstall immediately.
  • Workaround exists (disable orb via toolbar icon while keeping functionality) but is seen as non‑obvious.
  • Users want integration as a standard toolbar button or context‑menu entry, not intrusive in‑page UI.
  • Forced telemetry for the add‑on, and closed‑source code, further annoy tinkerers.

Local / BYO LLM vs Hosted

  • Repeated requests to:
    • Point Orbit at self‑hosted LLMs (e.g., Ollama) or local models.
    • Offer an in‑browser or on‑device model, especially given Mozilla’s own “llamafile” work.
  • Comparisons to Brave’s and Chrome’s AI features, which increasingly support local or BYO setups.

Mozilla’s Priorities, Finances, and Strategy

  • Large faction argues Mozilla should “just improve the browser” (performance, tab groups, vertical tabs, bug backlog) instead of side projects.
  • Others counter that Firefox alone is losing relevance and Mozilla must experiment to diversify revenue and stay competitive with AI‑enhanced Chrome/Edge.
  • Significant discussion of Mozilla’s dependence on Google search payments; some see projects like Orbit as “random fads” that burn resources; others see them as necessary risk‑taking.

Firefox vs Other Browsers and Features

  • Many say they’d rather see:
    • Native tab groups and vertical tabs (currently partially available via Nightly flags; widely handled by extensions like Sidebery, Tree Style Tab, Simple Tab Groups).
    • Better mobile Firefox (Android/iOS performance, feature parity).
  • Some praise Firefox: powerful ad‑blocking (uBlock Origin), manifest V2 support, privacy posture, better address bar and bookmark tools, and non‑Chromium engine.
  • Others report Chrome/Chromium browsers are noticeably faster and more reliable for heavy sites like Google Docs and YouTube; some have switched to Brave, Vivaldi, or Firefox forks (Zen, LibreWolf, Tor Browser, Mullvad).

Perceived Usefulness and Limits of Summarization

  • Split views on value:
    • Supporters see summarization as helpful for dense legal text, long articles, and video transcripts.
    • Critics argue LLM summaries are often inaccurate or vacuous; summarizing emails is seen as unnecessary or harmful to communication.
  • Broader worry that LLMs will bloat and then re‑summarize content, creating a loop of low‑signal text.