They just pushed an update on android on me that disabled all addons except uBO because they don't support them yet, a few hours ago.
That was the last straw that broke the camels back for me, after using FF since 1.0. Just rm -rf'd my firefox profile on my desktop a few minutes ago.
I've defended them for a long time even if I didn't agree with everything they did, but they're so completely off the rails, enough is enough. Blink mono-culture it is then.
The writing's been on the wall for a while now. I call it "The Mozilla Shuffle". Power features start out built into the menu. Then they get pushed to settings. Then they go to a key in about:config. Then you have to make the key yourself. Then they start ignoring the key but there's an extension that puts support back. Then the functionality which runs the extension gets disabled but if you're really determined you can work some magic with userChrome to get it back. Then you have to make keys in about:config to make it take the changes in userChrome. Finally, it's disabled entirely with no way to get back.
But hey, at least these days I get the benefit of having to use two completely separate methods to tell Pocket to get the hell out of my browser.
Wow, that's extremely accurate! Disabling the tab bar has also went this exact route (when you use a tiling wm with tabs, some people like to disable browser and terminal tabs as it's redundant)
I managed to do it with a combination of two extensions, some about:config flags and userChrome.css some years ago, but it may already be broken by now.
Mozilla keeps trying to get to the mainstream market while ignoring its dedicated users... The only times I got people to switch over to firefox was because things like ublock support on android. Nobody I've talked to has ever been interested in their side products (Pocket, that file transfer thing...), and something tells me this new voice engine is going to go the same route.
OTOH it's nice Mozilla is working on improving their voice dataset (which powers the DeepSpeech model, iirc). And again kind of sad they use Google Cloud while they could have their own version...
Disabling the tab bar is pretty easy. I use tree style tabs and they supply a couple of lines of css to paste into userChrome. You can even live debug userChrome using Inspector. The userChrome format did change about a year ago though.
They're paid something stupid like 100s of Millions of $USD to direct users to Google, and I understand the CEO was paid by Google (>$1M) though I've not seen good corroboration of that. Bias towards Google is not surprising.
Frankly it started going downhill when they jumped headfirst into the version number dick-measuring contest with Chrome. They care about pulling in new users, not keeping old ones. Anything to make a news headline and generate clicks and downloads. Some asshat feature one percent of their users will try one time and then never touch again. Disembowling their feature set to make a benchmark run five percent faster so they can make a graph with the biggest bar. Moral grandstanding about Google so a couple tech sites give them a mention.
It makes me so angry. Firefox was the chosen one. It slew the evil giant IE. Then Mr.moneybags Chrome came around and scared Mozilla so shitless they completely forgot why people chose them over IE in the first place. Their solution to every problem is "be more like Chrome while being less like Google".
Newsflash, Mozilla: you really suck at that. Maybe try something else.
> It makes me so angry. Firefox was the chosen one. It slew the evil giant IE. Then Mr.moneybags Chrome came around and scared Mozilla so shitless they completely forgot why people chose them over IE in the first place. Their solution to every problem is "be more like Chrome while being less like Google".
I totally agree. I feel so powerless watching them fail like that... Google annihilated firefox. Moral lesson here: free software can be destroyed. Not by openly fighting it, like Microsoft, but by rotting it from the core, like Google.
That's frankly a pathetic list when you consider not only the sum total of available extensions, but the list of Recommended Extensions alone. There's a Github issue for this with one particularly interesting reply: [1]
>Let it be put this way. I have extensions which I can already test while tethered using web-ext. They work. I know they work. But for some reason, Mozilla seems adamantly opposed to letting me test these extensions while not tethered to my computer.
That's from an extension developer who's struggling to test his own extensions.
Based on liuche's comments in that issue, the Fenix team's current stance seems to be, "The latest version disables some of the WebExtension APIs and adds some new ones which may break some extensions, so we're manually testing and approving every extension by ourselves, starting with the Recommended list. Sideloading unapproved extensions will probably never be allowed because of security and performance implications, except maybe on Nightly release."
I'm sure you can guess how well that's going to work out, given that only nine extensions are currently approved after 2+ months.
> Sideloading unapproved extensions will probably never be allowed because of security and performance implications
Very wise. They should apply those same principles to the Rust project - the code I write might very well have issues with security and performance, so it would be better if the compiler submitted it to Mozilla and awaited their approval before allowing me (or potentially not allowing me) to produce an executable.
>They just pushed an update on android on me that disabled all addons except uBO because they don't support them yet, a few hours ago.
It's worse than you thought. You just got the new Fenix browser they've been working on for some time, it's currently on staged rollout to stable channel. Old stable was Fennec and it's getting killed off. I know this because I've sat in their Matrix dev channel until today. I'm not sure what their priorities are, but it seems to not be focused on user.
While this submission was posted I spent the time filing a report to Mozilla because I brought up 3 specific concerns about this browser and wasn't sure where to file them (Bugzilla, Github issues, or now Jira?). Their Fenix Matrix channel responded by censoring my two messages in full and banning me for 'conspiracy theories'. So much for openness and inclusion. I was gonna save it up for a blog post but screw it, lets do HN, it's in your interest sphere:
First issue: I've been having occasional crashes with Fenix, this was why I was in their channel as I was hoping to get to the bottom of it. I installed it as Firefox Preview and they quietly updated to Nightly. This is sorta expected and fine I guess for beta quality software. The issue is I had all the data reporting stuff turned off. Browser starts crashing, sends a report to Mozilla (shows up briefly in android status bar, disappears). I don't know what it contains and this was highly concerning to me, so I listed this as a first issue as I don't want to be bitten for leaking client data every time the browser crashes. Where, why, and how are these being sent. Was it because I was now on Nightly channel and not Preview? I don't know how else to classify this other than user hostile behavior, in the same range of hostility as installing sponsored experiments without notification.
Second issue: One of the crashes happened while downloading. Every time I reopened the browser it'd re-initiate the download and crash again. Fenix doesn't have a working download manager other than to tell it to initially download. Sucks for you if you need to pause or view what was downloaded, there's no controls implemented. I expressed that this is likely to be a denial-of-service vector as I had to wipe the app's data to even use it again. It's also risky to users on metered service if it's continually pulling data attempting to re-initiate.
Third issue: for between 5 years (for Fenix) and 7 years (for Fennic) users have open bugs requesting pdfjs integration with mobile. Ability to inline pdf's in the browser has been a safari mobile feature since at least iOS 4 and possibly before, to the best of my knowledge it's always been a feature of Chrome. Desktop's pdfjs just got a promotion to first-class citizen last release. Someone wrote an extension to make the mobile browsers use it. Can't do that on Fenix anymore though, not because of a compatibility issue but rather because Mozilla won't allow outside addons anymore in Fenix without their blessing even if it's to use a product they've developed. Only way to override is build the browser yourself. Again, user hostile. If they don't want to add their own product, let us use an extension that adds it for us.
Finally regarding culture: I've been a part of IRC communities for a better part of a quarter century. I've also done HN for a few years now. I've gotten heated a few times in different communities, and been kicked or asked to leave. Forums I've had to remove content that was maybe a bit hotheaded. My interaction with Mozilla was literally the first time I've ever been censored and removed without a single word given in rebuttal. One of the things I love about HN is moderation knows when to step in and mods like Dan treat you like a human when those times occur. I can casually gripe some times about HN's preferences on topics, but the site works overall pretty well. The message I got from Mozilla is 'bot removed'. Here's their guidelines, they don't follow them (but I do, to be transparent I have this issue in their pipeline): https://www.mozilla.org/en-US/about/governance/policies/part...
To contrast, I've had to issue bugs to Chromium for browser issues and got nothing but decent things to say about their dev community there: You go to crbug.com and file an issue. I've had brief convos with some of their devs in Freenode IRC over some of the more buggy roll-outs (Aura was pretty crashy in the early days) and I guess the only thing you could say is they aren't very chatty. I'm concerned of course about Chrome eating the world but that's how it is. At least I understand Google's motivations. I don't understand Mozilla's anymore, they survive on Google money and are facing a continual bleed of users. Stuff like my first issue above is pretty major from user trust/legal liability standpoint and I don't appreciate being labeled a conspiracy theorist and censored for bringing up the behavior.
Issue 1: "Some fields, such as "URL" and "Email Address", are privacy-sensitive and are only visible to users with minidump access."[1] - So yes, you should not send crash reports when you are dealing with sensitive data.
Issue 2: That is unfortunate and should be fixed.
Issue 3: The issue for Fenix is not 5 years old, it is now one year old, see [2].
Regarding your ban:
- "I will not apologize for being spicy about these things"
- "It is a fact that you've made it intentionally difficult to use your own product to replicate functionality present in most browsers"
-> See the Mozilla Participation Guidelines - "Be respectful in all interactions and communications, especially when debating the merits of different options." [3] I guess you could have phrased things differently. I will not judge if this is "enough" to ban you, but I do also not know what you were posting before this specific comment, you mention additional comments.
Thanks for clarification on #1. It confirms what I was most concerned about and that was that my phone was leaking private info to Mozilla. On Linux I don't build the crash reporter, any crashes I used to backtrace and open with my distro first before moving to upstream. On mobile, Fennic had a specific option to turn off crash reporter, Fenix only has the two 'data sharing' sections.
I included the singular prior message posted the day before in my last comment on HN. I removed the part that was baseless in my second response which is what you saw.
@ #1: To be clear, I am not a Mozilla employee. So do not take this as a confirmation, I am just quoting the documentation.
@ "Fenix only has the two 'data sharing' sections." - You can always untick the checkbox in the crash reporter, see [1]: The data choice in the settings was removed in [2] and tickboxes were added at the same time in [3]. Fenix will also remember you crash reporting choice in the following crashes, you can test this yourself using - warning, this will crash your browser - about:crashparent.
Thanks for including your previous message: I think the ban was primarily based on your first message, but that is just my personal opinion. Hopefully you get more details from your report.
I mean, that’s the last text you sent. There was clearly other text you sent that was baseless speculation. There was history there you’ve not shown. Pretending as if this is the only text that mattered is dishonest.
I can see why they “banned” if you can’t even be honest to third parties.
>There was clearly other text you sent that was baseless speculation. There was history there you’ve not shown. Pretending as if this is the only text that mattered is dishonest.
Comments like this only further strengthens my point that rather than discourse this 'community' seeks to erase history and attack my credibility. Since Mozilla also censored it out and here's a screenshot of the original single text sent a day earlier: https://ibb.co/dgXBdJK
I handled all this (including attaching both screenshots) and more in my report to Mozilla. I don't believe it's dishonest to include the specific text that was censored amd banned when requested, especially when that text references the earlier 'baseless speculation' and I did not bring it up again. They asked what I was banned for, it was expressing my frustrations that caused me to send the original message in the first place.
Furthermore, its extremely concerning that the move to Matrix over IRC seems to be so that rather than just remove users they don't like, they can scrub the history of their message content and tag it with labels like 'baseless speculation' and 'conspiracy theories' to further debase the removed user.
I would include the text of the report I sent to Mozilla but it includes some personal information.
Kiwi Browser on Android supports Chrome extensions. After pushing the Firefox update that disabled my extensions, some of which I use when I buy groceries for recipes (Tap Translate), I am abandoning Mozilla too :(
Makes me sad after using Firefox for as long as I can remember, recommending it to people constantly and insisting that companies I worked at test in Firefox too, but I no longer trust Mozilla to do what's best for me.
Maybe they're only rolling it out for some users. I got it too and it was updated through some kind of internal update manager, not through the app store. Deleted my browsing history as well.
Switched over to Brave, as they have extensions on mobile cooking with POC videos on twitter. Hopefully they can accelerate it a bit. I think the HN crowd doesn't like brave though, idk, I do. IMO a lot of shit they get flak for are people not actually understanding. Like no, they don't replace ads on websites without their consent, or at least that's what they say.
So, because Firefox on your phone doesn't have X, you deleted it everywhere and installed a browser that... also doesn't have X?
FWIW This is one of the symmetries when we have to do policy shifts like TLS 1.0 deprecation. Even though every major browser will implement the policy and has announced that, some fraction of users will feel "betrayed" and switch from one browser implementing the policy to another browser also implementing the policy.
It's worse if you have defectors (e.g. back when Microsoft had Internet Explorer you could rely on IE being last to actually implement even if it had previously announced a timeline right in the middle of the ballpark, customers would push back and somewhere a Microsoft exec decides that hey, making a customer happy is more important than security) but it happens even for a more or less simultaneous policy change.
Guaranteed some CAs will lose customers over Apple's 398 day certificate expiry policy, even though it affects every CA equally at the same moment.
> So, because Firefox on your phone doesn't have X, you deleted it everywhere and installed a browser that... also doesn't have X?
No, because Firefox on my phone has removed X, I'm switchting to a browser that's getting X, and where the time-line isn't "we dunno lul". Maybe Brave doesn't hit their timeline, but Mozilla doesn't have one and I have no idea when my stuff will start working again. Until Brave Mobile has extension support I've downgraded my FF on mobile to the EOL version.
But as I said, it was the last straw that broke the camels back, I do not consider Mozilla to be trustworthy anymore, and this was just the latest in a series of issues.
I don't see how this is in any way similar to TLS 1.0 deprecation, because sites should have upgraded. There's nothing extension authors could have done. This is fully Mozilla dropping the ball (once again).
Except that FF is also getting the feature - according to their timeline around Q4 20 - Q1 21.
As many have pointed out, Mozilla updated your glitchy and slow browser with a newer and faster one that unfortunately still isn't at feature parity. They didn't remove the feature in the sense that they abandoned it, it was simply a regression that came with an update they considered more important. I agree it was way too soon to push Fenix to stable users, but switching to fancy Chrome just because of one FF regression that will be fixed seems a bit much.
That was the last straw that broke the camels back for me, after using FF since 1.0. Just rm -rf'd my firefox profile on my desktop a few minutes ago.
I've defended them for a long time even if I didn't agree with everything they did, but they're so completely off the rails, enough is enough. Blink mono-culture it is then.