Live data from Hacker News

Firefox 66.0.4 is out, fixes disabled add-ons

ftp.mozilla.org

231–240 of 392 posts

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#231

Earlier quoted context omitted.

Who's fault is that, at the end of the day? Mozilla didn't have to structure their addon system in such a way that their (in)actions could disable the addons of every Firefox user on the planet . Mozilla did not have to abuse the studies mechanism (also on by default) to ship a workaround. Mozilla did not have to disable the option that would let me work around this problem by myself (which is going to cause me no en…

"Opt-out telemetry" creates precisely the scenario I describe, where the users who care most are least visible to Mozilla, at which point their needs would go unconsidered; no one knows they exist, how many of them there are, or why they're opting out. This remains true regardless of why , which negates your entire list of issues, replacing them with a simple question that is very difficult to answer: How could Mozil…

>If you can't identify who your users are, you can't ask them questions, and you can't tell if they're "vocal 0.001%" or "vocal 40%" of your userbase — then what consideration could you give, as a software developer, for their needs?

I'd ask for feedback, and when that feedback is given freely, even when unsolicited, I'd take it on board and act accordingly. I would ask if people want to participate in "telemetry" and "studies", not assume they do without affirmative prior consent.

Mozilla is breathtakingly bad at this. They're about as responsive to feedback as GNOME/Freedesktop.

I most certainly would not put spyware in the product and turn it on without asking first. I'd most certainly never get myself into a situation where an oversight can simultaneously break every copy of my software ever deployed.

This idea that you require all copies of your software to phone home to make effective development decisions is bunk. We got along just fine without that garbage for decades.

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#232
post #113

I was already a bit mad at them for removing RSS support and claiming their proprietary service that's built in is an alternative, now their proprietary service keeps working (presumably, I didn't use it but it's not an addon so I doubt it's signed the same way) and I can't use the RSS addon. I know this was a mistake, but I can't help but be mad that their proprietary built in stuff effectively gets a free pass and…

Never hear Mozilla claiming anything about a prioprietary service being an alternative to add-ons. The reason for which built-in RSS support was removed is that it was much crappier than the add-ons available. Doesn't solve your problems, though :/

I can't find the link right now (I could swear I commented on the article here, but maybe I'm grepping for the wrong things in my comments), but in one of the blog posts where they announced removing RSS they advertised Pocket as the alternative that was still built in. Their RSS support was pretty terrible, but even so this sort of attitude was infuriating already, and now to see it have a leg up because they get to own the platform and the app just puts me over the edge. Not to mention that I have to dig through like three levels of settings to disable the damn thing and remove it from their stupid cluttered home screen every time something happens to my settings in the mobile version (which is alarmingly often).

I like Mozilla as a company, but I desperately wish there was an alternative sometimes. Anyways, sorry for the rant, I'm done (for now).

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#233

I was already a bit mad at them for removing RSS support and claiming their proprietary service that's built in is an alternative, now their proprietary service keeps working (presumably, I didn't use it but it's not an addon so I doubt it's signed the same way) and I can't use the RSS addon. I know this was a mistake, but I can't help but be mad that their proprietary built in stuff effectively gets a free pass and…

I use containers too. I didn't loose any data after I enabled dev mode and added the extension back. Perhaps you removed the existing extension first and lost data that way?

I did not disable or remove the extension, my containers were just all gone after the study was pushed and extensions came back.

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#234

About time. Embarrassing bug. The only reason i didn't permanently swap browser is because of the lack of alternatives since none has the functionality I apply through the addons.

I switched to the Dev build[1] with 'xpinstall.signatures.required = false', and now that it's fixed I don't know if I'll go back. There seems to be a bunch of new features in Dev that I assume will arrive in Firefox eventually, but everything else being equal, I think I'll stick with it. I'll probably turn 'xpinstall.signatures.required' back to true though. [1] https://www.mozilla.org/en-US/firefox/developer/

Mine says Developer edition beta 16 Version 67.0b16 (64-bit) Last updated = 03May2019.

do I need to make this change? is it in the about:config ? 'xpinstall.signatures.required = false

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#235
post #113

Earlier quoted context omitted.

Never hear Mozilla claiming anything about a prioprietary service being an alternative to add-ons. The reason for which built-in RSS support was removed is that it was much crappier than the add-ons available. Doesn't solve your problems, though :/

I can't find the link right now (I could swear I commented on the article here, but maybe I'm grepping for the wrong things in my comments), but in one of the blog posts where they announced removing RSS they advertised Pocket as the alternative that was still built in. Their RSS support was pretty terrible, but even so this sort of attitude was infuriating already, and now to see it have a leg up because they get to…

Found at least one place, though I don't think this was the post I was thinking of, pretty sure that was a blog (see "other alternatives"): https://support.mozilla.org/en-US/kb/feed-reader-replacement...

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#236

Earlier quoted context omitted.

> For example gating new things which could become a stability issue. And yet we were somehow able to ship stable software to millions of people in the days before telemetry/studies. What telemetry/studies truly provides is offloading QA costs to users.

The software was also simpler. And we were not really great to shipping stable software in the past.

Sure we were. I have video games that were pressed to CDs with no possibility of updates and they still run to this day. On a complete play through of many of them you wouldn't notice a single bug.

Using users for QA has made us lazy and borderline incompetent.

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#237

Earlier quoted context omitted.

Pocket was promoted as the replacement for RSS. Pocket is a closed source SaaS product, despite the fact Mozilla now owns it.

Huh? When was it promoted as a replacement, by whom? It’s not even in the same product category/ RSS aggregates updates to websites without needing to check them. Pocket takes an article you have open in your browser right now and saves a local offline copy on your phone. They’re apples and oranges. Apples and orangutangs, even.

Here (see "other alternatives"): https://support.mozilla.org/en-US/kb/feed-reader-replacement...

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#238

Earlier quoted context omitted.

You'll be several revisions' worth of security patches behind. For an application that is usually one's main means of accessing the rest of the internet, that would be a deal-breaker for me.

But even more security bugs behind.

Possibly, but I'll take the actively-developed codebase with the eyes of security experts all over it over one with no manpower.

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#239
post #138

Earlier quoted context omitted.

So when deploying changes it should just go to every single user with no incremental rollout?

Isn't that the entire point of the nightly and beta branches?

Those populations are not representative of the release population.
Post reply on HN