While user consent (default on vs default off, or any choice at all) is a different-but-related topic, Mozilla bake it all in, enable it all by default, and make it difficult to disable. (Settings would be “super easy” and would show it was intended as a permanent choice.)

These aren’t actions and design decisions indicative of having the best interests of users in mind. Especially given how closed the mobile client already is.

It seems to be designed in a way that leaves Mozilla the option of removing the ability to disable it, presumably if it becomes profitable enough and/or they think they can get away with it.

But for now on this point they get a pass from me on the desktop version in a personal environment where the user has the most control.