23 ms·
Chrome users beware: Manifest v3 is deceitful and threatening
- rektide 5y agoPreviously extensions could be background pages, with access to DOM & Web Platform apis. MV3 currently reduces them to Service Workers, able to use far far far less capabilities. This is a massive massive downgrade for Extensions, unfathomable really. A Mozillaian proposed a less limited Limited Events Page but Google has snubbed it & not discussed. https://github.com/w3c/webextensions/issues/134 https://github.com/w3c/webextensions/issues/134 Extensions are forced to use a small subset of JavaScript with no dynamic code execution. Eval() is banned. Function is banned. Embedding a scripting language inside JavaScript to circumvent this is banned. This is a mere ghost of JavaScript left over. Google claims it's to make it easier for them to insure extensions are safe & protect users, but just as much, to me, this is to protect Google from capable & competent extensions allowing users to expand their agency: now extensions have to be narrow, fixed use, specific extensions. Tools like GreaseMonkey are all dead. The web becomes no where near the hackable medium it is, all for a little convenience for Google. https://github.com/w3c/webextensions/issues/72 https://github.com/w3c/webextensions/issues/72 https://github.com/w3c/webextensions/issues/139 https://github.com/w3c/webextensions/issues/139 A lot has been said & discussed about MV3's declarativeNetRequest; this is where the visible war has raged in MV3 for a while now. I'm not a huge fan but it's also one of the more minor side-shows in this debate, to me. High impact on ad-blocking, but ultimately there's enough compromise & wiggle room here, enough possibility to make this not awful, and if things are left truly bad, there will be enormous hell to pay & this will blow up. DeclarativeNetRequest feels like a side show to how much real ruin & savagery is being wreaked by the first two issues I outlined, being wreaked upon the most powerful & interesting & defining software humanity has, that we augment ourselves with as we do software: our user agent extensions. I generally find Google to be quite a good steward for the web & am so happy they advance so many different initiatives & capabilities. But this is something that is extremely near & dear to me. The web is different & better than all other software, to me, because it is malleable, because the user-agent gives us power. MV3 is a radical curtailing of us the users. A radical shift towards a web that we have to simply accept, as is, that we cannot bend & shape as we want. Everything happening here feels abhorrent & disgraceful. The process also feels totally goofy. Google is simply flipping the switch next month. They built what they wanted to as a new spec, debated some about feedback, leave comments that oh yeah, we maybe do need to do something about GreaseMonkey, maybe we do need to fix some of the missing use cases, but we're going ahead with Apocalypse Now anyways. This is the most hostile use of standardizing to destroy that I have ever witnessed. If Google is having such a hard time hosting extensions as is, they need to stop. They need to close the Google Chrome Web Store for Extensions & stop trying to moderate it. Create a 3rd party store model, let other people serve as the agents of trust. They absolutely positively cannot be allowed to come along & standardize a much much much lower powered form of extension than what we've had, purely because they've had such a (sad fiddle) hard time running an extension store. Their justifications & pleading that these amputations to us are for our own good ring so very very false to me. Google needs to give up being a regulator of this power if it's too much for them.
- breezeTrowel 5y agoHave background pages ever had access to DOM? Usually all interaction with an observed tab is done through content scripts not background pages. Same goes for evaling JS code within the context of the inspected window.
- kevingadd 5y agoBy DOM access I assume they mean that since background pages are pages, you can do things like use IMG and SCRIPT tags to load resources, and perhaps a CANVAS to rasterize images that you then serve to pages via an extension URL or something. I've done stuff like that before so I can imagine there being use cases for it, but it's kind of niche.
- tentacleuno 5y ago> I generally find Google to be quite a good steward for the web & am so happy they advance so many different initiatives & capabilities. I don't. Especially not with FloC[0][1]. [0]: https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-idea https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-... [1]: https://developer.chrome.com/docs/privacy-sandbox/floc/ https://developer.chrome.com/docs/privacy-sandbox/floc/
- rektide 5y agoWhat else? As for FloC, still trying to understand FloC's implications & make a position on it. Hearing it proposed, it sounds enormously stupid, but I'm not convinced it's in fact bad. Part of me even thinks it indeed sounds like a significant privacy win over where we are. Rather than discuss FloC though I'm wondering what other efforts you would malign.
- Glench 5y agoWow, I kind of thought the headline would be an overstatement, but the article actually seems pretty even-handed and truthful in describing what's happening with Google's power over the browser market.
- breezeTrowel 5y agoI, on the other hand, found the article to be terrible. Consider the following quote: > Manifest V3, or Mv3 for short, is outright harmful to privacy efforts. It will restrict the capabilities of web extensions—especially those that are designed to monitor, modify, and compute alongside the conversation your browser has with the websites you visit. Under the new specifications, extensions like these– like some privacy-protective tracker blockers– will have greatly reduced capabilities. One would think that the article would then go on to detail exactly what these "new specifications" are and how would they reduce the capability of ad and tracker blockers. That never happens. We keep getting statements to the effect that Manifest V3 is bad but we're never told what makes it bad. What aspects of Manifest V3 limit ad blocker capabilities? Since Manifest V3 has been introduced way back in 2019 and, since then, has gone through various changes, are the quotes listed towards the end of the article recent or do they reflect an earlier version of V3? There was controversy over changes to the WebRequest API but that was two years ago and, I believe, changes have been made. Are there still changes that break functionality? What changes were made over the past two years? Have things gotten better or worse? The article gives absolutely no details.
- plorkyeran 5y agoThe article does not mention changes over the last two years because there haven't been any to mention. The new WebRequest API still does not support blocking requests (and still does support _recording_ requests), and the replacement for that functionality is still very limited.
- breezeTrowel 5y ago> The new WebRequest API still does not support blocking requests (and still does support _recording_ requests), and the replacement for that functionality is still very limited. Thank you. What you wrote is information that needs to be in the article but is not mentioned anywhere. The closest thing is a quote from Mozilla regarding their extensions security review process.
- HappySweeney 5y agoSo I guess someone will have to come up with a turn-key pihole-alike?
- mh- 5y agoNot even close to a replacement for the type of active, context-aware evaluation uBlock can do. Additionally, if a solution like Pi-hole was ever sufficiently mainstream, more sites would start serving their ads from the same hostname as the page. It's not difficult to do with the CDN providers most media sites already use.
- deleted 5y ago[deleted]
- cheschire 5y agoDoesn’t https and subsequently DNS over HTTPS effectively negate pi-hole? Honest inexperienced question.
- sofixa 5y agoHTTPS no, because you're still making regular old DNS queries for every domain, but DNS over HTTPS or stuff like Chromecasts using hardcoded DNS servers do effectively negate Pi-Hole.
- EvanAnderson 5y agoYes. Next you'll have to MiTM the DNS over HTTPS. Next in the arms race comes certificate-pinning. Controlling your name resolution will probably remain possible on Linux, but I expect most other platforms will make it exceedingly difficult for "normal" users. Embedded devices are already "game over". You don't own them (even if you paid for them). Controlling name resolution on your own network (and MiTM'ing HTTPS) makes you the same as a hostile nation-state actor. We can't have that.
- kelnos 5y ago> Embedded devices are already "game over". You don't own them (even if you paid for them). Ugh, seriously. I have a Chromecast, and couldn't figure out why it wouldn't play things on my local network (via DNS names set up in my router's resolver). Turns out Google hard-codes their own DNS servers and doesn't allow you to change them. The fix was to give the Chromecast a reserved IP address, and then set up some iptables rules on the router to redirect requests from it to 8.8.8.8 and 8.8.4.4 on port 53 to my router. I'm surprised that Chromecast is using old-school port-53 DNS and not DoH.
- ineptech 5y agoIf Chrome can kill uBlock and use its dominance to do user-hostile stuff, and Firefox goes along "in the interest of cross-browser compatibility", then what the hell's the point of Firefox in the first place?
- pkulak 5y agoMy assumption is that Firefox will be implementing the standard, but not the restrictions. Am I wrong there?
- amelius 5y agoFirefox also implemented DRM.
- pkulak 5y agoI needed them to do that so I could watch Netflix. Debate it all you want, but it made my life measurably better and I'm glad they did it. This would only negatively effect me (and everyone else).
- danuker 5y agoHow is your life measurably better, by comparing it with other people's fake and perfect and amazing lives (in Netflix videos)?
- Spivak 5y agoBecause some people don’t find digital DVD rentals to be an affront to their freedom and just want to watch Squidgame?
- handrous 5y ago> other people's fake and perfect and amazing lives Uh, if that's what we're supposed to be using movie and TV streaming services for, I've been watching precisely the wrong things. Seems more like a description of social media & (not unrelatedly) advertising. Or maybe porn.
- dessant 5y agoI have a couple of popular extensions on the line, and I no longer see a way to stop Google without immediate government intervention. I am confident that they are not acting entirely in good faith, regardless of the much needed and useful parts of Manifest V3. They will get away with anything, be fined again in a couple of years for the growing list of illegalities they commit, and now they'll also harm the browser extension ecosystem. Some of the extensions I maintain will no longer work, or have reduced functionality for no acceptable reason, and some of the projects that I have been preparing to release have now been abandoned, because they rely on having proper control over requests in the browser.
- kevin_thibedeau 5y agoMake them first class Firefox extensions.
- preinheimer 5y agoI mean you can, but firefox doesn't treat you any better. We waited 2+ months to get a minor update through review, and getting it through that quickly took emailing several folks (including one from HN). During that whole process they also removed the display of your queue position, making it even more opaque. At some point they disliked something in our extension that had been live for months, and disabled every release in the past year. At another point they found something wanting in a 2 year old release (not a recent one) and threatened to remove it from the store, our attempts to continue that conversation or just allow it to be pulled to save everyone some time met with crickets.
- skinkestek 5y agoAt this point I am seriously wondering if Mozilla is paid to drive Firefox into the ground.
- vorticalbox 5y agoThis does feel like it is the case doesn't it? I really want to like firefox but I hate it more with every release.
- tpmx 5y agoI've been using Chrome for such a long time now (since like a year after it launched), out of convenience and because it used to be fast (and more secure). It's definitely time to switch. I think my main alternatives are Brave, Vivaldi and Firefox.
- pkulak 5y agoPlease Firefox. The first two are just Chrome wrappers.
- tpmx 5y agoWell I like both Brendan and Jon, and I actively dislike Baker's leadership of Mozilla. However, Mozilla seems to have the highest investment level into the their desktop browser. I'll test Brave first.
- anewguy9000 5y agoYou realize Firefox only exists because it serves Google's interests right? And while Brave might be based on Chromium, it is distinct; in addition to not crippling nativewebrequest as chrome will, it's native adblocker is compatible with the same lists as ublock origin. So I would go with Brave :)
- deleted 5y ago[deleted]
- celsoazevedo 5y agoWhat will Brave, Vivaldi, etc, do when Google makes some change that breaks the current APIs? Do they have the resources and are willing to continue to support them?
- seph-reed 5y agoFWIW, Brave does.
- pkulak 5y agoIf Google actually gave a crap about security, they would let you disable extensions. As it is, I have to routinely delete malicious extensions from every family member's Chromebook. Lord knows how they get there, but they always do. Since this new standard still lets extensions observe everything, I don't see what the point is.
- technobabbler 5y agoPoint is they get to make ad blocking harder.
- pkulak 5y agolol, well, yeah.
- izacus 5y agoChrome allows you to disable installation of extensions via Group Policy for a looong time now: https://security.stackexchange.com/questions/66239/how-to-prevent-installation-of-google-chrome-extensions/192332 https://security.stackexchange.com/questions/66239/how-to-pr...
- deleted 5y ago[deleted]
- jsnell 5y agoThe security argument seems pretty simple. The end goal is that legit extensions that people regularly install should not need to ask for dangerous permissions, because a) it teaches the users that it's normal and b) since the extensions can become compromised later and abuse the permissions. Adblockers are probably the most common kind of extension, and are currently granted effectively unlimited access to read and modify every single web page you use. That's fucking scary. If adblockers (and other classes of legit and common extensions) can be migrated to a safe API, it makes the unrestricted and dangerous API much more manageable since what's left is much less likely to be legit or something people actually care about. For example you can have enhanced review processes, warn users more forcefully about the danger, start limiting the power of the API, implement new safe APIs for some of the remaining use cases, etc. EFF are smart people. They know what the actual security benefit is, and choose to instead argue against a caricature.
- bambax 5y ago> Adblockers are probably the most common kind of extension, and are currently granted effectively unlimited access to read and modify every single web page you use. That's fucking scary. How is that scary? The browser by definition has unlimited access to read and modify (and monitor) anything I do in it. And I trust gorhill a million times more than any Google employee, past, present or future.
- mappu 5y agoThe scary part is gorhill is able to sell or hand over the extension - as he has done in the past - to someone with looser morals and/or goals. How much do you think NSO Group would pay for this kind of access? If you ran uBlock Origin, would you like to retire early? Jbk from the VLC project has a lot of stories about turning down 6, 7 figure payments to bundle malware in VLC. Not everyone has the strong morals and unlimited stamina to withstand that. Manifest V3 is created to solve a real problem. I have had browser extensions go rogue on me before (Stylish), and i would like it to not happen again. At the same time, uBlock Origin is a hugely important extension for making the web usable for hundreds of millions of people. A compromise must be found that moves their safety out of a single person's hands.
- Havoc 5y agoWait FF is copying this too?!?
- zdragnar 5y agoSafari had the same concept first.
- Spivak 5y agoAnd ad blocking in Safari is fine, not great, but it works more or less.
- bambax 5y agoContent blocking on iOS doesn't work properly, many many things go through. Is it better on the desktop?
- SquareWheel 5y agoYep. But note that MV3 is a lot more powerful than Safari's adblocking capabilities. It's still declarative, but supports dynamic rules, header modification, etc. https://developer.chrome.com/docs/extensions/reference/declarativeNetRequest/ https://developer.chrome.com/docs/extensions/reference/decla...
- rektide 5y agoWeb Extensions have never had a spec before. So of course Google is taking the initiative to aggressively re-define & cut down what an extension is, at the exact moment they try to turn it into a cross-browser standard.
- zamadatix 5y agoFirefox is supporting Manifest v3 extensions however they are not imposing every limitation Chrome is on them and they are continuing to support features outside the scope of v3 like blocking webrequest. A lot of the changes in v3 are actually pretty sensible, it's just 10% of the stuff shoehorned in creating 90% of the friction. https://blog.mozilla.org/addons/2021/05/27/manifest-v3-update/ https://blog.mozilla.org/addons/2021/05/27/manifest-v3-updat...
- lunfard000 5y agoIt will be interesting what Microsoft will do, at first glance they don't care about advertisement and allowing ad-block would bring a lot of users to their ecosystem. (they already have soft adblock out of the box)
- account-5 5y agoThat probably because their operating system is infested with advertisements and data exfiltration mechanisms. Why would they need the browser to do it too?
- hunterb123 5y agoWhat!? Google acting in interest of ads and not users?!? Who cares? Just use Brave and kill Chrome off.
- donatj 5y agoI miss the early days of Firefox extensions (circa 2004) where an extension could in very powerful ways completely change the layout/functionality of your browser; when they had near unlimited access to the XUL and could change anything and everything. I used a ton of very useful extensions then. Nested tabs were one of my favorites. These days I've got a password manager, a bookmark checker, and a tab manager I wrote myself. They're just not allowed to do anything too useful these days - I know what they have access to, I write Chrome extensions. A lot of them should just be standalone desktop apps. Like most things, normies came in, shot themselves in the foot, made a fuss, and now we can't have nice things.
- power78 5y agoI wish Firefox would have left the old extension abilities. They could have easily added the WebExtensions standard to allow for cross-browser compatibility and not removed the old functionality.
- readflaggedcomm 5y agoThey basically did, until the underlying browser became incompatible. That was the point: to have a stable API instead of extensions relying on implementation details, which includes multiple processes.
- iggldiggl 5y agoThey didn't just broke them by necessity of rewriting the browser, though – they then actively blocked them on regular browser versions (non-Nightly/Developer Edition/etc.). Case in point: With some limited maintenance and a compatibility shim for loading them, a number of old add-ons are still working on current Firefox versions: https://github.com/xiaoxiaoflood/firefox-scripts/tree/master/extensions https://github.com/xiaoxiaoflood/firefox-scripts/tree/master...
- kevingadd 5y agoOnce multi-process was adopted, old extensions couldn't work anymore. The design simply didn't work.
- judge2020 5y agoWhile a good message that does have actual merit if you know what's happening already, I don't see how this is a legitimate consideration of MV3. The entire argument regarding security doesn't mention any of the reasons Chrome developers cite its security improvement, instead it brings up that Firefox "does good enough already" and that malicious extensions can still get past the review process. the review process is by itself improved with V3 as extensions that pull in code remotely can no longer get past the review process[0], especially with how many current extensions implement RCE C&C intentionally. They also say extensions are "usually interested in simply observing the conversation between your browser and whatever websites you visit" - that's 'usually', though; malicious extensions intercepting and modifying requests for their own benefit isn't unheard of. Instead of only stating 'this is bad', it would be beneficial to include both (A) what they say (B) their basis for the decision, if any (C) why that line of reason is incorrect/deceiving. 0: https://developer.chrome.com/docs/extensions/mv3/intro/mv3-overview/#remotely-hosted-code https://developer.chrome.com/docs/extensions/mv3/intro/mv3-o...
- syrrim 5y agoBeneficial in what sense? If manifest v3 is still bad on net, then including chrome's counter arguments makes for bad rhetoric and thus does a poor job of advancing a valiant goal.
- kevingadd 5y agoAnyone who pays attention to the web platform should know by now that any rationale Chrome (or Google in general) developers give for web platform decisions is made up. They repeatedly told us they had specific motives for AMP and it was all a lie, AMP was designed to tighten their grip on the advertising market. It's not the only example - the way their autoplay whitelist works is also transparently manipulative despite lies to the contrary - and I would bet money that MV3 is partially motivated by business incentives in the same way. Googlers' paychecks are signed by Ads and GCP and ad-blockers actively undermine the former.
- yonixw 5y agoGoogle has not provided any reason to not include "block request" functionality. And that the super bad faith underlying fact that poison their "reasoning".
- aeharding 5y agoManifest v3 is a shit show. https://github.com/w3c/webextensions/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc https://github.com/w3c/webextensions/issues?q=is%3Aissue+is%...
- ilaksh 5y agoOne option is to just move away from browsers entirely. We can take some of the good things. Like maybe a small subset of HTML and web assembly. Add some minimal IO to web assembly.
- tux1968 5y agoA website being rendered by opaque, per-site web-assembly code, is not going to be amenable to uBlock, Greasemonkey or any other user-empowering extensions.
- ilaksh 5y agoIn this theoretical world you would generally not authorize any code (nor could any run by default) if you were just trying to view a web page. The HTML subset would be used for displaying information.
- polote 5y agoI honestly think that Google underestimated how much they are going to piss off users with MV3. There are thousands of extensions that will stop working and be impossible to build. But also there will be a lot of broken experiences as remote loading is forbidden and fixes will need a new release. Can't wait, but that's a very good opportunity for Firefox as Firefox will become more powerful than Chrome
- csdvrx 5y agoOr more likely, towards Edge, by virtue of requiring almost no effort to deploy the same set of extensions in a very similar browser in the hands of a company who doesn't require destroying privacy as much as google does to keep making money.
- nvrspyx 5y agoIIRC, the Edge team said they would adopt manifest v3, but correct me if I'm wrong.
- deleted 5y ago[deleted]
- sharken 5y agoThis page intended for developers of Edge extensions seems to support your statement: https://github.com/MicrosoftDocs/edge-developer/blob/main/microsoft-edge/extensions-chromium/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md https://github.com/MicrosoftDocs/edge-developer/blob/main/mi...
- ComputerGuru 5y agoWell, Firefox is adopting it too but not breaking the old manifest support at the same time.
- cube00 5y agoOne of the "benefits" to Microsoft of using Chromium is reduced development costs and they're not going to get that if they let the forks diverge too much.
- gnicholas 5y agoDoes anyone know how the Manifest v3 changes will affect extensions that modify pages for accessibility reasons?
- porkbrain 5y agoAs long as those extensions don't fetch and execute any JavaScript that hasn't been bundled at the time of Chrome store submission, they'll be fine. The biggest change happens at the API for monitoring and managing web requests.
- kevingadd 5y agoGenerally speaking it shouldn't impact them, but it may make them more awkward to use. And the developers will have to change a lot of code.
- eitland 5y agoMentioning again to the entrepreneurical ones here that I want to pay money for something that works like old Firefox but uses the new supposedly more secure code base. I pay for IntelliJ so why not pay for the just as important browser if I can get one that I like? Just don't increase the pricing to Jetbrains level until you have Jetbrains level features.
- foxrider 5y agoI'd pay for Vivaldi if I had to at this point, it's the only browser that feels "feature-complete" to me
- eitland 5y agoIs it Chromium based? It might be great but for now refuse to support anything that further strengthen Googles grip on the market.
- KronisLV 5y ago> It might be great but for now refuse to support anything that further strengthen Googles grip on the market. The question then becomes: "What else even is out there?" Because if you're looking for something that's even remotely feature complete for browsing the modern day web, the majority of the current browsers out there are indeed based on Chromium, as expressed in this article, "Firefox is the Only Alternative": https://batsov.com/articles/2021/11/28/firefox-is-the-only-alternative/ https://batsov.com/articles/2021/11/28/firefox-is-the-only-a... Here's the table from the article in text format: Browser Based on Chromium Open-source Market Share (desktop + mobile) Chrome Yes No 64.7% Chromium Yes Yes - Edge Yes No 4.0% Brave Yes Yes - Vivaldi Yes No - Opera Yes No 2.4% Safari No No 19.0% Firefox No Yes 3.7% To me it seems like Firefox is the only viable alternative and putting all of our hopes on a singular browser and the company behind it, especially given that there has recently been some controversy around it, seems risky. For example: https://itdm.com/mozilla-firefox-usage-down-85-but-why-are-execs-salary-up-400/2050/ https://itdm.com/mozilla-firefox-usage-down-85-but-why-are-e... and https://arstechnica.com/information-technology/2020/08/firefox-maker-mozilla-lays-off-250-workers-says-covid-19-lowered-revenue/ https://arstechnica.com/information-technology/2020/08/firef...
- lobocinza 5y agoTwo weights and two measures.
- davidhyde 5y ago> “ It’s also doubtful Mv3 will do much for security. Firefox maintains the largest extension market that’s not based on Chrome, and the company has said it will adopt Mv3 in the interest of cross-browser compatibility.” I don’t understand why Firefox needs to adopt Mv3 for “cross-browser compatibility”. Is this to save extension writers time and effort or is it a mistake in the article?
- sfink 5y agoThe former. Firefox tries to make it possible to port Chrome extensions to Firefox with minimal changes. Mv3 contains lots of new stuff beyond nerfing adblockers.
- Animats 5y agoBecause of this, sometime in 2022 I will shut down Sitetruth, my fifteen year old ad blocking and site evaluation system. That offers add-ons for Chrome and Firefox, and puts a tag with company background info on each search result. Some search ads are removed, and some are de-emphasized. Some time next year, Google will probably force that add-on out of Chrome, as they tighten their grip over what browsers are allowed to do. I did this as a technology demo, to demonstrate automated site background checking. The concept that you have to have a business address to sell online is almost archaic now, even though it's the law in the EU and California. So, today often the system often can't tie a web site to business records. The concept of "legitimate business" is dead.
- rizky05 5y agoJust build an electron browser, you can control whats going on inside in.
- 1vuio0pswjnm7 5y agoI was working on a project about 15 years ago that could tie a website to a business address. The underlying assumption is that many/most legitimate businesses that sell products have registered trademarks. The main purpose of a mark is to enable traceability back to a legitimate, non-ephemeral source for a product. If the reader disagrees that reputable products would have associated trademarks, then stop reading here. :) These trademarks can be represented in a domain name or TLD. IP offices that register the marks generally obtain physical mailing addresses for physical correspondence. The crux of the idea is that the domain name and TLD do not have to be issued by ICANN. As such, it does not have to follow any pre-established conventions. Trademark registration systems already have unique identifiers and classifications that can be represented in the domain name/TLD. Thus we can create a new, collision-free naming system that offers more than ICANN, e.g., a direct association to an IP office.^1 This leverages the work of IP offices to collect business addresses (or at least addresses of the registrant's lawyers/agents who would by necessity have the business address of the registrant). Under this system the perceived legitimacy of the business is reliant on the trademark registration, not a "TLS certificate". The legitimacy of the domain name/TLD becomes dependant on the trademark registration, not an unaccountable, known-to-be-corrupt entity such as ICANN. To put it simply, names require an associated trademark. The system favours businesses that want to enable consumers to trace a product back to an original, legitimate source. It is a naming system for real(TM) business. :) Personally, if I were trying to assess the legitimacy of a business, I would rather rely on the records of a trademark office versus the records of a TLS certificate provider. But that's just me. 1. ICANN of course, to ensure its own profits, chose to allow disputes to occur and create quasi-legal dispute resolution systems instead.
- outside1234 5y agoIs Edge going to continue allowing blocking of requests?
- jakub_g 5y agoIIRC Brave and Vivaldi stated they will keep Mv2 support. I wouldn't bet on other vendors though.
- rasz 5y agoVivaldi didnt. All they said was they wont remove anything themselves aka it will be removed when it vanishes from Chromium codebase. Vivaldi cant afford to maintain their own fork of v2 code, they barely manage the UI as it is.
- throw7 5y agoThe article is not exactly well written. I don't really follow web developments anymore because the web, well, sucks; So, after reading, I'm still not even sure what "manifest v3" is about and why I should care. I know websites track me. I know I get tons of ads. I know websites popup questions about cookies. I know they play videos that follow me around when I scroll. I know sometime in the past that shit would've been under my control. But I suppose I have rose-colored glasses on and that's just the way it is. After all, I remember blink tags.
- trissylegs 5y agoIt's for Browser extensions. Chrome extensions (and also Firefox and Safari). a fail called the "Manifest" that tells Chrome and the extension about the extension and contains all it's permission requests. Eg: "This extensions wants to modify all webpages", which is what ad blockers need to do. Going forward extensions in the Chrome Web store will have to use Manifest v3. Which has less capabilities than previous version. Which will stop ad blockers working. tl;dr. Ad blockers will not longer be possible in Chrome.
- ahahahahah 5y agotl;dr Extensions with embedded spyware will no longer be able to record all of your web use. Malicious ones that steal credentials will be more easily identified. These types of extensions are installed far, far more than ad blockers.
- rasz 5y agoWhy would you spread misinformation? V3 removes Blocking part, but doesnt touch Inspecting - every extension can still snoop on all traffic.
- AnonC 5y ago> tl;dr. Ad blockers will not longer be possible in Chrome. This is not completely true. Ad blockers like uBlock Origin that allow specific elements to be picked and blocked wouldn’t be allowed. All the requests (like ads) to be blocked would have to be declared in a list (like Safari Content Blockers, and presumably have a limit on the number of rules). The actual blocking will be done by the browser without the extension knowing which rules were applied to which pages.
- 1vuio0pswjnm7 5y ago"Like FLoC and Privacy Sandbox before it, Manifest V3 is another example of the inherent conflict of interest that comes from Google controlling both the dominant web browser and one of the largest internet advertising networks." Thank you to the author for getting to the point: conflict of interest. Google cannot represent ("protect") users and sell to advertisers at the same time. No amount of blog posts/marketing/propaganda/arguing in forums can change that. Advertisers are paying Google for services, users are not. Google's entire racket has become heavily dependent on these conflicts. Google believes it must gain/preserve "user trust". Google wants users to believe it is on their side. That is what con arists must do. Remember when other browsers announced they would not adopt FLoC. Websites also announced they would disable it as a courtesy for users through use of the Permissions-Policy response header. https://wordpress.org/support/topic/add-interest-cohort-to-permissions-policy-to-block-google-floc/ https://wordpress.org/support/topic/add-interest-cohort-to-p... https://github.blog/changelog/2021-04-27-github-pages-permissions-policy-interest-cohort-header-added-to-all-pages-sites/ https://github.blog/changelog/2021-04-27-github-pages-permis... https://paramdeo.com/blog/opting-your-website-out-of-googles-floc-network https://paramdeo.com/blog/opting-your-website-out-of-googles... https://scotthelme.co.uk/what-the-floc/ https://scotthelme.co.uk/what-the-floc/ DevTools still warns this is an "unrecognised feature". Does interest-cohort=() even work. Perhaps it does but in some jurisdictions FLoC is enabled by default in Chrome. The user has to manually disable it. Assuming the user evens knows what it is. https://github.community/t/i-have-no-idea-what-the-interest-cohort-is/179780 https://github.community/t/i-have-no-idea-what-the-interest-... I found the CFTC, for example, has a nice usage of the Permissions-Policy header, better than the Guardian. www.cftc.gov permissions-policy: accelerometer=(),autoplay=(),camera=(),clipboard-read=(),clipboard-write=(),fullscreen=(),geolocation=(),gyroscope=(),hid=(),interest-cohort=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=() www.theguardian.com permissions-policy: camera=(), microphone=(), midi=(), geolocation=(), interest-cohort=() But really, how much can anyone rely on something like this. Users have no meaningful control over this browser. It is changing all the time, and "features" are tested on different groups of users, without ensuring their informed consent. Sure, a user extension may work now, but whether it works in the future is not within the user's control and, most importantly, Google's interests and the user's interests are almost certain to conflict. "Google's efforts to limit that access is concerning, especially considering that Google has trackers installed on 75% of the top one million websites." I have learned to enjoy blocking Google's incessant attempts to phone home. Google is curiously obsessed with TLS, so substituting a self-signed certificate for Google websites can actually be one of several ways to stop these connections, letting them fail at the proxy. It seems Google really does not want users to see what data Chrome is trying to send to Google. I wonder why. Someone recently showed me an interstitial page they got while logging into Gmail, asking for their date of birth. It was very deceptive. It asked the user to "help us comply with the law" or some such. Of course, it was optional (the cookie had already been sent and the user was already logged in, unbeknowst to her) but there was no indication to that end. It appeared to be mandatory. The user was led to believe she could not proceed without entering a date of birth. A company with millions in cash reserves behaves like con artist who cannot get a real job. It is impossible for me to take this seriously as business. A massive con. Yes. An honest business. No.
- svnpenn 5y agoTo anyone saying "just use Firefox", I would think again. I think Firefox is (marginally) better than Chrome, but they are also pulling some of the same bullshit: https://github.com/mozilla-mobile/fenix/issues/20736 https://github.com/mozilla-mobile/fenix/issues/20736
- kaba0 5y agoA technical decision (on mobile) you didn’t bother looking into is not even remotely in the same ballpark as what google does. Calling firefox marginally better than chrome is just dishonest, and frankly ridiculous.
- svnpenn 5y agoapparently you didnt bother you read my comments on the linked issue, as well as the multiple issues I linked to it, including one that I opened myself [1]. My own issue was closed as wont fix. 1. https://github.com/mozilla-mobile/fenix/issues/20647 https://github.com/mozilla-mobile/fenix/issues/20647
- Mathnerd314 5y agoTo be fair, Firefox is the most popular of the 3-4 browsers that lets you install addons on Android. So the fact that the process is convoluted and tedious is less important - at least there's a process.
- redleggedfrog 5y agoI'm super impressed with Google's attention to Hacker News and getting their shills to come in and muddy the waters and refute. At least one guy admitted he's working for the man...
- deleted 5y ago[deleted]
- perryizgr8 5y agoThe main issue is user choice. If I want to run an extension, no matter how malicious, on my machine, I should be able to do it. This applies for my phone too, which is a capable computer for all practical purposes. Apple has normalized the "we know better" approach, and has enjoyed great success doing it. Google is simply following that same philosophy. They know better than you, what's good for you and what's bad. We need a fully independent browser, open-source, and built on modern technology. That way, users who care about this can get what they want. And users who trust Google to get it right, can use chrome or one of its derivatives. Firefox has (had?) that potential, but for whatever reason Mozilla seems unable to execute effectively. The result is that Firefox has become a follower, doing the same things Chrome is doing. Thus defeating the original motivation for users looking for an alternative. Brave looks promising, but given that they build on top of chromium, I am not sure how long they can resist fundamental changes in the codebase. Or whether they even intend to provide the needed alternative. All in all I feel this represents a sorry state of browsers, and consumer software in general.
- KevinMS 5y agoI remember the old days when HN users would promote the hell out of chrome. They loved it, couldn't get enough of it. A few others, including myself, were like... um guys, this browser is created by a company that makes its money from advertising that shows in browsers, do you really think this is going to turn out well?
- ShamelessC 5y agoYou may see this as naive, but there was more confidence in Google (and big tech in general) to continue to "do no evil" in those days. I personally have never been upset with my firefox experience after their big re-write a few version back. The only benefits I see with chrome lately are when sites are clearly designed and tested only for Chrome. Not much of a benefit in the grand scheme of things, obviously.
- Bellamy 5y agoAnd you believed a multinational stock company. I hope you don't make that mistake again.
- ShamelessC 5y agoUh, okay - I was like twelve at the time so I try not to be too hard on myself (or others) for making similar mistakes. I'm not sure which part of my comment gave you the impression that I had not learned my lesson. Did you just feel like being rude to a random stranger? Or do you really think it's productive to go around blaming victims for getting grifted by professional grifters?
- deleted 5y ago[deleted]
- deleted 5y ago[deleted]
- ianmf 5y agoWhen Google Chrome came out, it was fast, reliable, secure, and it was not Internet Explorer. Chrome was what everyone needed back then. The competition was Firefox, which performance was getting slower (before Quantum). The problem was that Google shifted priorities for Chrome (or played the long game) to better support Google/Alphabet's interest.
- Tempest1981 5y agoIt's also a major problem for many extensions, since ServiceWorkers (can) get killed every 5 minutes. No talk of a solution, just people trying hacks. https://bugs.chromium.org/p/chromium/issues/detail?id=1152255 https://bugs.chromium.org/p/chromium/issues/detail?id=115225... Example of breaking long-runnng classroom extensions used in education: (comment 63) https://bugs.chromium.org/p/chromium/issues/detail?id=1152255#c63 https://bugs.chromium.org/p/chromium/issues/detail?id=115225... And breaking a simple image picker: (comment 36) https://bugs.chromium.org/p/chromium/issues/detail?id=1152255#c36 https://bugs.chromium.org/p/chromium/issues/detail?id=115225...
- pastacacioepepe 5y agoYes this is the craziest part of the transition from V2 to V3. V3 is still bugged. I crashed chrome by setting the incognito key to "split", and turns out there's no way to be sure that when you open an incognito page, your extension will be awake. What a mess. I will postpone the "upgrade" the most I can, then I suppose I'll be forced to write a desktop app and pay hefty licenses to Microsoft/Apple. Google is just ignoring the complaints and the bug reports.
- kome 5y agostop using spyware like chrome* or brave*. * https://spyware.neocities.org/articles/chrome.html https://spyware.neocities.org/articles/chrome.html * https://spyware.neocities.org/articles/brave.html https://spyware.neocities.org/articles/brave.html
- hda2 5y ago.. or firefox* * https://spyware.neocities.org/articles/firefox.html https://spyware.neocities.org/articles/firefox.html Off the three, brave seems the least worse one in terms of telemetry and the best in terms of respecting it's users' wishes. All are considered spyware by that site.
- kome 5y agono, false, brave remains problematic, Firefox is the only one with more more privacy potential. With Firefox the user has much more freedom to modify important settings, while Brave remains spyware. https://spyware.neocities.org/guides/firefox.html https://spyware.neocities.org/guides/firefox.html
- hda2 5y agoNo, it really isn't and I've shown you why. If one of these browsers is spyware, both are.
- gerash 5y agoThe article is hollow but from what I understand the gist of the issue is: Google is cutting down on the extensions ability to read and modify your web requests on the fly. As a side effect adblocker type extensions need to pass their blacklist patterns to chrome which will enforce it on their behalf. Chrome cites improved privacy because users won't need to give random extensions full read write access to pretty much all their online activities and performance gains because arbitrary adblocking code cannot run anymore and it needs to be in form of a blacklist patterns. Lastly Apple Safari has been doing the same all along. The opponent arguments (expressed in the article and by many people leaving comments here) are that this kneecaps some AdBlock extensions because they need to run arbitrary code as the declarative API is not flexible enough for them and this is part of Google covert plan to kill adblocking. I personally agree with the Chrome team's argument here
- kaixi 5y agoExtensions will still be able to read all the requests, just not block them, so Google's argument for privacy is moot. Given that one of the biggest performance hogs are the ads and tracking scripts on a page, the argument for performance seems sketchy too. I don't use adblockers myself, as I actually like seeing ads, but Google's arguments are very weak here.
- darknavi 5y ago> as I actually like seeing ads I've learned of a new kind of people today. What about the "ad experience" do you like?
- AnonC 5y agoA lot of comments here are wondering what Firefox will do and if uBlock Origin would be made useless in Firefox like it would be in Chrome (once Mv3 is implemented). Short answer: Firefox is adopting various parts of Mv3, but will continue to support blocking webrequest, which is used by extensions like uBlock Origin. So uBlock Origin would become useless in Chrome, possibly Edge and a few other browsers, but not on Firefox. Quoting from this update [1] from Mozilla: > Google has introduced declarativeNetRequest (DNR) to replace the blocking webRequest API. This impacts the capabilities of extensions that process network requests (including but not limited to content blockers) by limiting the number of rules an extension can use, as well as available filters and actions. > After discussing this with several content blocking extension developers, we have decided to implement DNR and continue maintaining support for blocking webRequest. Our initial goal for implementing DNR is to provide compatibility with Chrome so developers do not have to support multiple code bases if they do not want to. With both APIs supported in Firefox, developers can choose the approach that works best for them and their users. > We will support blocking webRequest until there’s a better solution which covers all use cases we consider important, since DNR as currently implemented by Chrome does not yet meet the needs of extension developers. [1]: https://blog.mozilla.org/addons/2021/05/27/manifest-v3-update/ https://blog.mozilla.org/addons/2021/05/27/manifest-v3-updat...
- winternett 5y agoChrome has just been getting worse and worse over time, but if you can recall, Firefox was also a slug when it was at a peak of market dominance and before that MSIE... The problem is that orgs and companies stop caring once they gain the primary market share. They also start dictating standards to everyone and ignoring user feedback. It's symptomatic of our current software development driven economy. I recall when as a web dev I had to ensure my code was best supported by 3-4 browsers and don't miss that era at all, but it would be much better if proper regulation, consumer protection, and ethical corporate behavior came into play before hostile competition, corruption, and monopoly-driven "dictatorware" do in software market dominance for a change.
- Karunamon 5y ago
- pabs3 5y agoI'd like to see the Firefox DevTools turned into an official user-controlled adblock system for Firefox. It has pretty much all the things you would need; control over the requests, control over the responses, control over presentation, control over JavaScript flow etc.
- mrtweetyhack 5y agoMozilla is just as bad selling to the highest bidder.
- jacquesm 5y agoTranslation: FireFox is now irrelevant to Google's business other than as an anti-trust fig-leaf. As a browser, it is no longer a threat.
- tptacek 5y agoIt's hard to take EFF seriously when they write so hyperbolically. What's clearly also the case is that Chrome extensions are one of the great modern security and privacy challenges --- to the point where multiple tech company security teams have people whose job it is just to screen them. Another detail that EFF doesn't want to share is that ad blockers are some of the worst offenders --- they demand maximal access to user data (think about how they work), and there are lots of them, not all of them, uh, implemented scrupulously. EFF doesn't want to give you the other side of this story, because they're not an honest interlocutor. If you had the other side of the story, you might still think Manifest v3 was a bad deal. Random ad blockers are very dangerous, but there are ad blockers that everyone trusts, and you might not want to make it harder for them to maintain their projects. But EFF doesn't trust you to make that decision on your own.
- veeti 5y agoThere is no decision left to make once this change goes through. You can talk about improved security all you want, but the fact remains that uBlock Origin will be permanently crippled. This by far negates any security or privacy gain that Manifest v3 could possibly make. Switch to Firefox.
- hyperman1 5y agoThis is in fact one of the best arguments pro to do the change: * Chrome destroys ad blocking * Advanced users now suffer the same internet as everyone else * Advanced users will find a solution, and that solution can't be chrome anymore * This starts an exodus of advanced users . * Advanced users configure the browsers for everybody else, hence everybody else also joins the exodus The end result is less of a monopoly. This is the same mechanism that ultimately killed of IE and moved everybody to chrome: The monopoly of the time got so arrogant they didn't listen to their users, so users fled to a better alternative. The strange thing is, groups of people have more or less the same tolerance for abuse, know their limits have already been violated for a while, and learn alternatives from each other. As a result, It takes a long time of abuse to trigger an exodus, but when it started, it starts everywhere at the same time. Then the abuser tries stopping the exodus by rolling back only the last change, but that's not enough anymore.
- Cpoll 5y agoSemi-related question: Does anyone have a workflow for version pinning Chrome extensions? GSuite Admin lets you allowlist extensions, but I haven't seen a way to fix an extension to a trusted version.
- Hackbraten 5y agoIn both Chrome and Firefox for Linux, you can create and maintain a package for your system-wide package manager that wraps your extension at whatever version you like. Example: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=chrome-token-signing https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=chrom... Not sure about other OSes, though.
- mediumsmart 5y agoGoogle is in the user data business and chrome is their browser. I don’t feel deceived.
- sirius87 5y agoI can see why Chromium-based browsers such as Vivaldi (non-opensource) are increasingly baking in features of popular extensions into the browser (ad-blocker, dark mode). First, there's the risk of Chrome Web Store simply not being available to non-Chrome flavours. Next, the extensions APIs and ecosystem could head in any direction Google wants. I use about 6 extensions, 3 of them self-compiled and sideloaded (JSON Viewer, Dark Reader, Violentmonkey). I wish services like Pushbullet would open-source their browser extension. Isn't all the secret sauce on the server-side anyway?
- Bellamy 5y agoOpera, Brave, Firefox, even DuckDuckGo browser works pretty well. There is really no need to use Chrome anymore.
- josephcsible 5y agoWhat's even the point of switching away from Chrome if the browser you're switching to is also Chromium-based and closed source?
- afiori 5y agolimiting Google tracking
- londons_explore 5y agoWhile I don't want to give Google PR tips here... There is a much smarter way for Google to achieve their aim... Make the new manifest optional. Point out that malicious extensions keep using the old manifest (which is more powerful and allows far more evil things). Allow web developers to set a "disallow less secure extensions" http header. That allows banks and stuff to ensure an insecure old-manifest chrome extension isn't redirecting all your funds to North Korea while you do online banking. Before long, ad networks will realise that setting this header nerfs adblockers too. Most of the web will set the header to get more ad revenue. In the press, it will be the evil people misusing the secure header rather then Google's fault.
- marderfarker2 5y agoThe day Chrome (and it’s derivatives) kill my extensions, is the day I switch to Firefox. I cannot live without my adblocking.
- einr 5y agoThey're boiling the frog. It will get gradually more inconvenient, but still kind of viable, until the day they pull the plug entirely. The day that happens, Firefox is likely no longer a viable option and it is too late. If you care about the open Internet, the entire point of switching is to do it before it's too late. The writing has been on the wall for years now.
- timbit42 5y agoThat day will be too late. The time to switch is before it happens to discourage it from happening. It's really too late even now.
- nathias 5y agoWho could have imagined that if you give the whole of the market share to an add-salesman he would prevent you from blocking adds.
- skepticoitus 5y agoTIL that there is this whole DeGoogle movement. I luv muh privacy as much as the next guy. But the posters to the Reddit sub of that movement come off sounding "emotion-driven" at best. Conspiracy theory "extremists" at worst. The impression I get from the Reddit discussion of the eff.org article [0] is that the majority of posters there are not "Hackers". That can be a good thing in a way. One not-so-good thing, on the other hand, is /r/degoogle posters' apparent unfamiliarity with the nuances sometimes involved in software maintainability decisions. That plus the confirmation bias that is inevitable in any subreddit. I'm far from a Google fanboy. Trust me! But being somebody who does code reviews on the regular, I can understand why Google played the "Single purpose" policy constraint card as their rationale for pulling that AdNauseum extension. [1] From a quick review of the AdNauseum code [2] I can see why Google would say that it does more than one thing. Case in point: It could be argued that my word processor provides a "Single purpose". Namely: Process words. But my word processor actually has several discreet functions that I use it for: Mail merges, PDF generation, script and manage macros, etc. So in that sense, my word processor does not provide a "Single purpose". I could see how Google could apply that to AdNauseum. *************** [0] https://web.archive.org/web/20211212051743/https://old.reddit.com/r/degoogle/comments/rcwbks/chrome_users_beware_manifest_v3_is_deceitful_and/ https://web.archive.org/web/20211212051743/https://old.reddi... [1] https://web.archive.org/web/20211209223531/https://adnauseam.io/free-adnauseam.html https://web.archive.org/web/20211209223531/https://adnauseam... [2] https://github.com/dhowe/AdNauseam/ https://github.com/dhowe/AdNauseam/
- skepticoitus 5y agoTIL that there is this whole Degoogle movement. I luv muh privacy as much as the next guy. But the posters to the Reddit sub of that movement come off sounding "emotion-driven" at best. Conspiracy theory "extremists" at worst. The impression I get from the Reddit discussion of the eff.org article is that the majority of posters there are not "Hackers". That can be a good thing in a way. One not-so-good thing, on the other hand, is degoogle posters' apparent unfamiliarity with the nuances sometimes involved in software maintainability decisions. That plus the confirmation bias that is inevitable in any subreddit. I'm far from a Google fanboy. Trust me! But being somebody who does code reviews on the regular, I can understand why Google played the "Single purpose" policy constraint card as their rationale for pulling that AdNauseum extension. [0] From a quick review of the AdNauseum code [1] I can see why Google would say that it does more than one thing. Case in point: It could be argued that my word processor provides a "Single purpose". Namely: Process words. But my word processor actually has several discreet functions that I use it for: Mail merges, PDF generation, script and manage macros, etc. So in that sense, my word processor does not provide a "Single purpose". I could see how Google could apply that to AdNauseum. *************** [0] https://web.archive.org/web/20211209223531/https://adnauseam.io/free-adnauseam.html https://web.archive.org/web/20211209223531/https://adnauseam... [1] https://github.com/dhowe/AdNauseam/ https://github.com/dhowe/AdNauseam/