See what’s changing in Firefox: Better insights, same privacy | The Mozilla Blog
blog.mozilla.org
Innovation and privacy go hand in hand here at Mozilla. To continue developing features and products that resonate with our users, we’re adopting a new a

To disable it in about:config

browser.search.serpEventTelemetry.enabled  =  false	
browser.search.serpEventTelemetryCategorization.enabled  =  false
  • kbal
    3•7 months ago

    Speaking of large numbers of user comments, I was just reading the hacker news discussion. Whatever you think of that site, it’s full of the sort of people who used to be the core of the Firefox user base. People who would help their friends and family get it installed. Web developers who made sure their site works with more than one browser engine. People who know enough to be offended by changes like this one. People who Mozilla needs to reach if it wants to have a future in the web browser market.

    Comments elsewhere are similarly negative. I encourage everyone who cares about Firefox to turn off all the telemetry, or perhaps even consider moving to one of the forks such as Librewolf. If they notice enough of a drop in incoming data collection after this latest move, perhaps there’s still a chance that Mozilla will get the message that they need to change course before it’s too late.

    • @blii@lemmy.zip
      1•7 months ago

      I think I share your view about course correction needed but if anything this seems to be a step in the right direction, I really do not see how Mozilla is being unreasonable (with this feature). To have a chance at the market outside of core geeks some telemetry is needed, and if we truly think that anonymoused (not connected to session, IP, or user, only distinguishable from others by timestamp of when data was recieved) counters based on a few narrow categories, then I think the userbase is a part of the problem.

      should we really protest when they are doing it right? are we not being unreasonable if we take the stance that no telemetry is allowed?

      the only step in a more privacy-direction I can see this feature taking is if it is opt in by default, but this being so incredibly trivial non identifiable info, I think maybe it’s better for all parties for those to just use Librewolf then