|
|
|
|
|
by Causality1
2144 days ago
|
|
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. |
|
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...