Comment by edelbitter

Comment by edelbitter 2 days ago

4 replies

View on Hacker News

Its not just that each new "feature" is unnecessarily difficult to disable, and already active-with-privacy-side-effect by the time you notice.

Most new "features" are by now covered by an existing setting and/or policy. Yet I recognize a pattern of introducing new "but did you opt out of THIS NEW thing?" or "but did you opt out of VERSION TWO of this previously rejected thing?" setting/policy. It has become unsafe to upgrade to new Firefox releases, because each one will disrespect previous user choice in another unexpected way.

hekkle 2 days ago

If you don't want new features, don't upgrade it, what in the non-sequitur is this? I get the argument that it SHOULD be OPT-IN rather than OPT-OUT, but that would require annoying pop-ups every upgrade that explains the new features and ask if you want to OPT-IN. That is more burden on the developers and will annoy more users than benefit.

If you are concerned, they do have what is called a 'changelog' that will explain all of the new features and how to switch them off if you like.

Reply View 3 replies
  • zzo38computer 2 days ago

    You might want some of the new features (such as TLS 1.3, WebP, some security fixes, etc), but avoid some others (such as HSTS, many new web APIs, secure contexts, AI, some CSS commands, etc), and want to keep some features that are removed in later versions (such as several settings, and many other things).

    Reply View 2 replies
    • hekkle a day ago

      You're right, you may want some features but not all of them. That is why firefox provides the flags for you to turn features on/off. You mention that a user might wast "TLS 1.3, WebP, some security fixes, etc". I would argue that if a user knows what these are, they are capable of working out a flag.

      Reply View 1 reply