Switching to Firefox costs $0 and works on every network, not just your home net.
Only if you don't value your time. This would at least require me to search for equivalent plugins.
An Exercise Program for the Fat Web
11–20 of 35 posts
Re: An Exercise Program for the Fat Web
#12Earlier quoted context omitted.
DNS over HTTPS against a server you can't choose would do so, yes.
You could still shut down the initial DNS query for the dns-over-https provider and make it unreachable
Some people refuse devices that do not accept DHCP assigned DNS servers.[1]
[1] https://mailarchive.ietf.org/arch/msg/dnsop/WCVv57IizUSjNb2R...
Re: An Exercise Program for the Fat Web
#13Switching to Firefox costs $0 and works on every network, not just your home net.
It's also hella buggy on macOS for me, which is irritating - my browser is the only thing I need to work 100% of the time. As much as I'd like to reduce Google's browser monopoly, I consciously choose to make this one exception.
Have you tried brave? Not sure if it has feature parity, but it is a new take on a chromium based browser.
Re: An Exercise Program for the Fat Web
#14> It's kind of scary how powerful DNS can be, isn't it?
And that, I think, is why we see a push for DNS-over-HTTPS and other things: because eventually Google (and other device manufacturers) will only use the network-provided DNS servers to find their DNS servers. And of course your device will only use Google's servers, for your security of course.
You might think that sounds crazy, but we've already seen it come to pass: Android apps will now ignore owner-supplied root certs. This means that the device owner cannot inspect HTTPS traffic sent by his own device.
The endgame is that we're not really owners of our own computing devices, but simply renters of media-consumption appliances.
Re: An Exercise Program for the Fat Web
#15Switching to Firefox costs $0 and works on every network, not just your home net.
It's also hella buggy on macOS for me, which is irritating - my browser is the only thing I need to work 100% of the time. As much as I'd like to reduce Google's browser monopoly, I consciously choose to make this one exception.
Define hella buggy? What's not working for you?
(apart from the obvious recent f-up with the addon signing obviously, which—while glaring—was at least a one-off)
Re: An Exercise Program for the Fat Web
#16Switching to Firefox costs $0 and works on every network, not just your home net.
It's also hella buggy on macOS for me, which is irritating - my browser is the only thing I need to work 100% of the time. As much as I'd like to reduce Google's browser monopoly, I consciously choose to make this one exception.
Any particular bugs that are annoying you? The main one for most people seems to be excessive battery consumption on retina displays, which is being worked on (requires switching the renderer interface over to Core Animation, so is understandably taking a while). Apart from that I can only think of minor annoyances compared to some of the problems with Chrome like major memory consumption and the gradual strangling of personal privacy extensions.
Re: An Exercise Program for the Fat Web
#17Switching to Firefox costs $0 and works on every network, not just your home net.
Only if you don't value your time. This would at least require me to search for equivalent plugins.
Firefox has some better plugins and features, like container tabs. You can block ads with the built-in tracking protection, uBlock Origin (not uBlock), and uMatrix.
Re: An Exercise Program for the Fat Web
#18Switching to Firefox costs $0 and works on every network, not just your home net.
Only if you don't value your time. This would at least require me to search for equivalent plugins.
You’ll find that a lot of the extensions are the same ones, now that Firefox has switched over to Chrome’s WebExtension model as a base.
Re: An Exercise Program for the Fat Web
#19Earlier quoted context omitted.
It's also hella buggy on macOS for me, which is irritating - my browser is the only thing I need to work 100% of the time. As much as I'd like to reduce Google's browser monopoly, I consciously choose to make this one exception.
Any particular bugs that are annoying you? The main one for most people seems to be excessive battery consumption on retina displays, which is being worked on (requires switching the renderer interface over to Core Animation, so is understandably taking a while). Apart from that I can only think of minor annoyances compared to some of the problems with Chrome like major memory consumption and the gradual strangling o…
Add-on context menus display only when launching them through overflow menu, it doesn't work when I put the icon next to the navbar.
I have a smaller DPI non-retina MBP2012 and I always set the default page size to 80% in Chrome. I used two extensions for the same functionality in Firefox (Fixed Zoom and a second one that worked a bit better) but I always had issues with the sites being bigger than the viewport and having to scroll around them to see the content. Images were the biggest victim to this behaviour.
You are right - there are issues in Chrome, but I don't feel them as much in my day to day life and it counts for me.
Re: An Exercise Program for the Fat Web
#20Earlier quoted context omitted.
It's also hella buggy on macOS for me, which is irritating - my browser is the only thing I need to work 100% of the time. As much as I'd like to reduce Google's browser monopoly, I consciously choose to make this one exception.
Any particular bugs that are annoying you? The main one for most people seems to be excessive battery consumption on retina displays, which is being worked on (requires switching the renderer interface over to Core Animation, so is understandably taking a while). Apart from that I can only think of minor annoyances compared to some of the problems with Chrome like major memory consumption and the gradual strangling o…
It's slow and eats a lot of battery on Mac. It's a known issue.