10 ms·
Wow, this is much worse than I assumed: > In fact, we were able to circumvent the issue just by changing the name of the Chrome app on a Windows desktop. It se
by crazygringo 4y ago
Wow, this is much worse than I assumed:
> In fact, we were able to circumvent the issue just by changing the name of the Chrome app on a Windows desktop. It seems that Microsoft threw up the roadblock specifically for Chrome, the main competitor to its Edge browser.
From the beginning of the article, I was led to believe Microsoft had changed an API around checking/setting the default browser to show Microsoft's dialog instead. Which doesn't seem great to change an API without warning, but maybe you can make an argument that it ensures a "neutral" choice rather than apps pushing the choice on users.
But this shows it's specifically against Chrome. Regardless of whether it's legal or not, it's unforgivably anti-competitive behavior. It's a truly shameful tactic.
- Paul-Craft 4y agoIt looks like they're going back to the days of "DOS isn't done until Lotus won't run," alright. Very shady.
- runlevel1 4y agoThere was a post on here about that phrase a few years ago: https://news.ycombinator.com/item?id=10432608 https://news.ycombinator.com/item?id=10432608 Lots of interesting discussion in there, even if the phrase didn't come out of Microsoft as the article anecdotally suggests it didn't.
- nr2x 4y agoGiven that Chrome is aggressively pursuing privacy sandbox, which is roundly rejected by everybody in the web privacy community, is aggressively user hostile, and designed solely as a means to leverage chrome’s (current) dominance to support google ad business, it’s fair to start treating chrome as malware.
- AlexandrB 4y agoWhat part of this description of privacy sandbox doesn't apply to what Microsoft has been doing with Windows? I think it's time to treat Windows 11 as malware as well.
- rjzzleep 4y agotechnically those two are not mutually exclusive
- evandale 4y agoHonest question, why is the privacy sandbox user hostile? I assume it's because Google is using it to collect your information but blocking everyone else from collecting it?
- simplotek 4y ago> Honest question, why is the privacy sandbox user hostile? From the horse's mouth, "privacy sandbox" is explicitly designed "to build thriving digital businesses." https://privacysandbox.com/intl/en_us/ https://privacysandbox.com/intl/en_us/ At face value they claim it's designed to eliminate tracking techniques like fingerprinting, it's actually a system explicitly designed to collect the users' private information. From the horse's mouth. "To provide this free resource without relying on intrusive tracking, publishers and developers need privacy-preserving alternatives for their key business needs, including serving relevant content and ads."
- edoceo 4y agoSo, it's tracking just not intrusive tracking?
- simplotek 4y agoIt sounds like it's plain old tracking, but pushed and owned by Google through it's control over Chrome.
- thewataccount 4y agoNo it's objectively less intrusive. The proposals involve reducing UA data, ip tracking, etc. But still allows for some amount of targeting. From my understanding instead of you being an identifiable individual via fingerprinting, the aim is to make you "probably one in [large group] of technology people". I'm not saying I think it's a good thing, but on the surface it does appear _better_.
- 4y ago
- charcircuit 4y agoHow is it user hostile when it protects people's privacy while also meeting the needs of advertisers? It's a win win.
- ocdtrekkie 4y agoIt is definitely about meeting the needs of advertisers, by implementing new methods to violate user privacy. Every other browser has simply blocked advertisers from collecting this information, but Google is an ad company, and hence is anti-consumer at heart.
- TechBro8615 4y agoBecause in reality, "meeting the needs of advertisers" is not a prerequisite to "protecting people's privacy." It's a false premise that Google constructed and which only exists because the dominant browser is created by an advertising company. A browser that truly protected people's privacy would definitionally not meet the needs of advertisers, because those needs are in direct opposition to people's need for privacy.
- charcircuit 4y agoProtecting people's privacy is not the sole job of a browser. The web in general needs to look at the needs of all of the stakeholders and come together to find a solution that all parties can find agreeable. A browser should care about not just the users, but also the rest of the people in the ecosystem. If Chrome shipped an update that blocked all ads it would kill many sites and would cause a disaster to the health of the web ecosystem. Chrome should try and improve the ecosystem.
- JohnFen 4y ago> A browser should care about not just the users, but also the rest of the people in the ecosystem. Hard disagree. A browser is supposed to be my user agent. It is supposed to work for me. It should not be engaging in compromises to my wishes in order to benefit others. > Chrome should try and improve the ecosystem. I think that there is much disagreement about what "improving the ecosystem" would look like.
- gigel82 4y agoThat's true, but Edge is literally the same codebase and architecture, rebranded and with slightly tweaked UI, plus additional MS tracking. So Edge should get the exact same treatment.
- nr2x 4y agoSince people seemed to believing Google PR at face value here is the w3c position in rejecting the proposal: The intention of the Topics API is to enable high level interests of web users to be shared with third parties in a privacy-preserving way in order to enable targeted advertising, while also protecting users from unwanted tracking and profiling. The TAG's initial view is that this API does not achieve these goals as specified. The Topics API as proposed puts the browser in a position of sharing information about the user, derived from their browsing history, with any site that can call the API. This is done in such a way that the user has no fine-grained control over what is revealed, and in what context, or to which parties. It also seems likely that a user would struggle to understand what is even happening; data is gathered and sent behind the scenes, quite opaquely. This goes against the principle of enhancing the user's control, and we believe is not appropriate behaviour for any software purporting to be an agent of a web user. The responses to the proposal from Webkit and Mozilla highlight the tradeoffs between serving a diverse global population, and adequately protecting the identities of individuals in a given population. Shortcomings on neither side of these tradeoffs are acceptable for web platform technologies. It's also clear from the positions shared by Mozilla and Webkit that there is a lack of multi-stakeholder support. We remain concerned about fragmentation of the user experience if the Topics API is implemented in a limited number of browsers, and sites that wish to use it prevent access to users of browsers without it (a different scenario from the user having disabled it in settings). We are particularly concerned by the opportunities for sites to use additional data gathered over time by the Topics API in conjunction with other data gathered about a site visitor, either via other APIs, via out of band means, and/or via existing tracking technologies in place at the same time, such as fingerprinting. We appreciate the in-depth privacy analyses of the API that have been done so far by Google and by Mozilla. If work on this API is to proceed, it would benefit from further analysis by one or more independant (non-browser engine or adtech) parties. Further, if the API were both effective and privacy-preserving, it could nonetheless be used to customise content in a discriminatory manner, using stereotypes, inferences or assumptions based on the topics revealed (eg. a topic could be used - accurately or not - to infer a protected characteristic, which is thereby used in selecting an advert to show). Relatedly, there is no binary assessment that can be made over whether a topic is "sensitive" or not. This can vary depending on context, the circumstances of the person it relates to, as well as change over time for the same person. Giving the web user access to browser settings to configure which topics can be observed and sent, and from/to which parties, would be a necessary addition to an API such as this, and go some way towards restoring agency of the user, but is by no means sufficient. People can become vulnerable in ways they do not expect, and without notice. People cannot be expected to have a full understanding of every possible topic in the taxonomy as it relates to their personal circumstances, nor of the immediate or knock-on effects of sharing this data with sites and advertisers, and nor can they be expected to continually revise their browser settings as their personal or global circumstances change. A portion of topics returned by the API are proposed to be randomised, in part to enable plausible deniability of the results. The usefulness of this mitigation may be limited in practice; an individual who wants to explain away an inappropriate ad served on a shared computer cannot be expected to understand the low level workings of a specific browser API in a contentious, dangerous or embarrassing situation (assuming a general cultural awareness of the idea of targeted ads being served based on your online activities or even being "listened to" by your devices, which does not exist everywhere, but is certainly pervasive in some places/communities). While we appreciate the efforts that have gone into this proposal aiming to iteratively improve the privacy-preserving possibilities of targeted advertising, ultimately it falls short. In summary, the proposed API appears to maintain the status quo of inappropriate surveillence on the web, and we do not want to see it proceed further. https://github.com/w3ctag/design-reviews/issues/726#issuecomment-1379908459 https://github.com/w3ctag/design-reviews/issues/726#issuecom...
- grishka 4y agoWhat surprises me about this stuff is that no one has ever tried to get a definitive answer to this sort of question with the help of reverse engineering. It's always this guesswork for some reason. It does not have to be guesswork when the ground truth is right there inside your C:\Windows folder.
- Kye 4y agoI don't know why it's surprising. Reverse engineering an executable is quite a jump in skill level from guesswork.
- nneonneo 4y agoThat, and Windows is *huge*. The best bet would probably be to reverse engineer the patch in question, but if it’s a typical combo patch then you’re probably looking at changes across a dozen system files. If you’re unlucky, the patch is just flipping a flag or something for a feature that already existed: it wouldn’t surprise me if Windows already had hacks specifically for “chrome.exe” (for compatibility or anti-compatibility reasons). In that case it becomes much more time consuming to isolate the one component that is responsible for the problem.
- deleted 4y ago[deleted]
- saagarjha 4y agoI’d reverse engineer the API they were calling. Generally this kind of thing yields good results quickly.
- userbinator 4y ago"Reverse engineering" is vague and means anywhere from "poke at it randomly to see what it does" to "read the binary".
- justinclift 4y ago
- yrro 4y agoNothing new under the sun. Edge ain't done 'till Chrome don't run...
- dmix 4y agoCan Google sued Microsoft for doing this? I'd imagine the Justice Dept might come calling if Edge takes #1 spot in the future.
- neonsunset 4y agoCan Google be sued by Microsoft in return for breaking YouTube for years on non-Chromium browser?
- DANmode 4y agoYes.
- DANmode 4y agoYes. Any chance you're familiar with their last antitrust suit?
- kenjackson 4y agoExcept the world has changed a lot in 20 years.
- bombcar 4y agoAnyone can be sued for damn near anything; but can they win a suit? That would be a harder one.
- 908B64B197 4y agoI posted this below, but I suspect the scoping for Chrome.exe was done because Chrome was misusing an API. According to the article: "the worst was reserved for users on the enterprise version of Windows. For weeks, every time an enterprise user opened Chrome, the Windows default settings page would pop up. There was no way to make it stop unless you uninstalled the operating system update. It forced Google to disable the setting, which had made Chrome more convenient." Enterprise maybe didn't like settings getting changed that way (conflict with group policy?). If it was constantly opening new windows, it's probably because it was constantly calling an API (probably in the wrong or an undocumented way). So it would make sense to change how the API works based on a known bugged application. It wouldn't be the first time Windows changes how something works based on application name [0]. Keep in mind there's also more than just the documented Win32 API exposed to applications on Windows (and who knows if Chrome was misusing these undocumented ones) [1]. [0] https://devblogs.microsoft.com/oldnewthing/20031224-00/?p=41363 https://devblogs.microsoft.com/oldnewthing/20031224-00/?p=41... [1] https://learn.microsoft.com/en-us/sysinternals/resources/inside-native-applications https://learn.microsoft.com/en-us/sysinternals/resources/ins...
- jamesfinlayson 4y agoChrome has used an undocumented Windows API before: https://www.hanselman.com/blog/the-weekly-source-code-33-microsoft-open-source-inside-google-chrome https://www.hanselman.com/blog/the-weekly-source-code-33-mic... After someone noticed this the comment was mysteriously deleted from the Chrome source code.
- saagarjha 4y agoBrowsers use undocumented APIs all the time. Doing so is unfortunately close to necessary.
- 908B64B197 4y agoBut it can lead to instability. There's a reason these are not documented. Also, we know Chromium used some. There's a proprietary Chrome layer on top of it that might be using more under the hood. Unless someone decompiles there's no way of knowing (but considering how it broke Enterprise, wouldn't be surprised it was doing undocumented stuff under the hood).
- surgical_fire 4y agoIn a fight of Microsoft against Google, I support the fight.
- kbenson 4y agoI don't. In a fight we all as end users lose. Competition is beneficial to the end user, fighting, where they sabotage each other or bar each other or their own apps from platforms is not. Did end users benefit when YouTube was blocked from being used on Amazon Firesticks? Did they benefit when Roku and HBO were feuding and you couldn't use HBO Max on Roku devices? Be careful what you wish for.
- tremon 4y agoIn Dutch we have a saying "when two dogs fight over a bone, a third runs off with it". I support the fight if it will weaken both Microsoft and Google.
- saagarjha 4y agoOf course, the third dog need not be better than the other two.
- fractalf 4y agoI thought about it. Carefully. If google and microsoft went bankrupt tomorrow i wouldn't miss a thing and would be feel abundance of joy. The world would be a much better place without then.
- kbenson 4y agoThat's a combined 400,000 employees out off a job in one day. I wouldn't wish that hardship on those people all of a sudden, and that's before we consider the wider ramifications to the economy from those people being unemployed. Then there's all the people and companies, non-profits and NGOs that use theiur services which would run into major problems. I would be be tempted to think perhaps you just glossed over that, because the alternative appears to be a complete lack of care for others, but as you've noted you've thought about it. Carefully.
- moogly 4y agoIt's quack.exe all over again.
- andirk 4y agoOr virus.exe as seen on Office Space.
- 29athrowaway 4y agoIt is exactly as I assumed. It is 100% consistent with everything Microsoft does. https://googleblog.blogspot.com/2011/02/microsofts-bing-uses-google-search.html https://googleblog.blogspot.com/2011/02/microsofts-bing-uses... https://www.theregister.com/2003/02/06/msn_deliberately_breaks_operas_browser/ https://www.theregister.com/2003/02/06/msn_deliberately_brea...
- ilyt 4y agoIt's funny, every now and then (at least in gaming circles) there is always some fanboy yelling "but MS isn't the old evil company as they were, look, they did X or Y". But it's just same bullshit under new manager. MS. MS never changes.
- userbinator 4y agoI prefer the "old evil" MS. At least they weren't so eager to participate in massive surveillance of their users, unlike the "new" MS.
- ilyt 4y agoOh that's only because tech wasn't there yet, 90's MS would totally do.
- userbinator 4y agoBack then, they wanted to be selling a product, not turning users into the product.
- type0 4y agowrong, the tech was there, but users' expectations weren't - it's a sad state of affairs really
- monocasa 4y agoSo, total rumor, but I've heard from a few sources on the grapevine that one of the reasons for their antitrust spat with the DoJ was actually as a proxy battle, and the main thing the DoJ cared about was Microsoft's unwillingness to play ball wrt data collection and "lawful intercept". The sense I've gotten is that Microsoft of the time really did have a very libertarian core thought process that wasn't really into spying on it's users.
- marlor 4y agoYes. That is indeed a total rumour.
- chillfox 4y agoEh, both Google and Microsoft have been using dirty tactics against each other for awhile. Remember the entire reason Microsoft scrapped their own browser engine was because Google kept breaking YouTube video acceleration in Edge/IE.
- jacooper 4y agoAnd how google killed windows phone on purpose
- themoonisachees 4y agoUnclear as to how but as a windows phone user (there were dozens of us!) I say good riddance.
- dannyw 4y agoBorking things like google maps and email based on windows phone user agent when it works fine if you change the user agent.
- FormerBandmate 4y agoThey’re both wrong
- Spivak 4y agoYes but in this specific case Google is more wrong. MS implemented a security feature where user applications aren't allowed to change the default browser. You can disagree with it and it's sketchy as hell but it's there and supposedly to prevent the bundled-with-java problem. Breaking it is basically guaranteed to lead to plugging the hole and blacklisting the misbehaving app is easier than getting out the real fix. You can be all like "rebel chrome is taking on big operating system" and that's fine and makes total sense but "how dare MS enforce their own rule" is a weird take. You can't be like "hey, they weren't supposed to do it back" when you intentionally abuse your elevated privs to bypass security measures.
- keyle 4y ago"Embrace, extend, and extinguish"
- usernew 4y ago>it's specifically against Chrome I have not encountered any other browser that has a button like Chrome put in. Back in the day, a browser and email apps could set themselves as default, on their own. A long time ago. This was bad. I don't want an app to be able to make itself default for something, and just magically trust that the app will ask me first. There is an OS control for that - I don't want apps to be able to do that on their own. So MS fixed it, and all was good, for a long time. Chrome then somehow found a sneaky way to get that back. Truly a shameful tactic. Well guess what "google" - you're not allowed to do that, and there's a reason the functionality was removed for all apps. You're just a browser app, I don't want you to screw with or even have access to screw my OS settings. Microsoft fixed a security hole. Good on them. For now, they specifically fixed it for the malicious actor. Hopefully they'll fix it OS-wide eventually.