Earlier quoted context omitted.
Agreed on hoping this is the inflection point, but only partial agreement that it's about adblock. For sure Google wants adblock to die, but I think it goes even deeper than that. I think it's part of a much bigger trend in tech in general but also in Google: Removing user control. When you look at the "security" things they are doing, many of them have a common philosophy underpinning them that the user (aka device…
> To all the engineers working on this stuff, I hope you're happy that your work is essentially destroying the world that you and I grew up in. I recently quit my job, developing among others the means to "protect" media using DRM. While this was not a primary motivation, I'm glad to somewhat clean my hands. The technology (dubbed Common Encryption) is a bunch of smoke and mirrors that a childishly easy to hack aroun…
"Begin disabling installed extensions still using Manifest V2 in Chrome stable"
201–210 of 490 posts
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#202Earlier quoted context omitted.
The widespread adoption of Chrome was largely driven by word of mouth, people like you and I installing it on our friend's/relative's computers and telling them it was safer/faster/better. Nothing stops us from doing the same thing again. I've been recommending Firefox to all my family/friends/colleagues for years (ever since I've seen the writing on the wall for Chrome). While Firefox isn't perfect, it's in a much b…
>The widespread adoption of Chrome was largely driven by word of mouth No, it was driven by having a banner in the most privileged spot of the Internet, Google.com (the most visited site in the world with 0 ads on the homepage) saying that was faster and more secure than the alternatives. In fact Firefox benefited from some free ads on Google.com against Internet Explorer before Google developed Chromium.
Later Google's ability to buy installs and put it on google.com came into play, but for at least the first 5 years and probably longer, chrome was a far faster, more secure, and more reliable choice. They also pioneered the multi-process model to isolate different components of the browser.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#203can i just setup dns blocking on my network to block the ad requests? especially on youtube, ublock origin stopped working a few weeks ago.
First, exceptions are at the domain level. So you can't say "allow this domain on this site", you have to blanket-allow a domain or not.
Second, the UX for making exceptions isn't great. With uBO it's just a couple of clicks. With something like Pi-hole it's more complex: https://discourse.pi-hole.net/t/how-do-i-whitelist-or-blackl...
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#204Hopefully this is the inflection point for Chrome. Despite all their made-up "security" reasons, everyone knows this is solely about making adblock less effective. For many users, adblock is what makes chrome bearable - and if they make it unbearable, then those users will leave. Slowly but surely. Google seems much too sure of itself making this change. I hope their arrogance pays off just the same as Microsoft's di…
> everyone knows this is solely about making adblock less effective I thought I knew that. Then I switched from uBlock Origin to uBlock Origin Lite in Chrome, which is compatible with Manifest v3. I was prepared for the horrible onslaught of ads, expecting at least a quarter would start getting through, ready to switch to Firefox... ...and didn't notice a single change. Not a single ad gets through. And at the same t…
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#205Earlier quoted context omitted.
On the contrary, MV2 used onBeforeRequest which let extensions see what requests you were making. They could then take that data and use it for malicious purposes. MV3 doesn’t allow extensions to know what requests are being made, so extensions can’t use your data maliciously. Requests to ads that are blocked are blocked. I think you’re thinking of Privacy-preserving ad measurement which is an option in Firefox and S…
Doesn't onBeforeRequest still exist in Manifest v3? The thing that's been removed is the ability to block on it, not the ability to register handlers for requests.
Now, if an ad blocker has webRequest permissions it’s a red flag.
For example https://developer.chrome.com/docs/extensions/develop/concept... uses webRequest to send telemetry back to some remote server.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#206I switched from firefox to chrome for their superior devtools a few years back, but hopefully firefox has had time to catch up.
Everything old is new again!
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#207Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#208Earlier quoted context omitted.
The Android version of Firefox still doesn't have working keyboard shortcuts after 13 years or a way to delete individual history items to prevent broken auto complete. The money is going into lots of other things than the browser.
I'm not sure keyboard shortcuts for a version designed to run on an OS for devices without keyboards will ever be a priority. You can use a keyboard on an Android device, but the vast, vast majority of Android devices are phones that never get used with keyboards. I don't expect there's much priority to adding that feature. I agree that a lot of money is going to things other than the browser though.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#209Earlier quoted context omitted.
To my knowledge the “big” chrome engine alternatives aren’t either. I know that Vivaldi and Brave plan on keeping around v2 as long as it is economically feasible
This sounds like Android phone manufacturers making fun of apple for removing the headphone jack and then doing it themselves a year later. Are they seriously going to maintain V2 support for a relatively small percentage of Powerusers which probably are mostly already using Firefox anyways? The point of being economically infeasible is probably in a month or so.