6 ms·
Mind you, another way to say that is “malicious extension authors can no longer snoop on all network traffic.” As someone who was, at one point, pitched a proj
by derefr 7y ago
Mind you, another way to say that is “malicious extension authors can no longer snoop on all network traffic.”
As someone who was, at one point, pitched a project proposal for a browser extension our company could make which would “make users think they’re getting one useful effect, while secretly using their browser as a node in a distributed web-scraping farm to social-network sites they’re logged into” — I’m sure this is more common than people think, and very wary of extensions saying they do one thing while doing quite another (which happens to fit into the same permissions set as the explicit purpose of the extension, making users none the wiser.)
- CodeCube 7y agoI'm curious if you wouldn't mind sharing what was the context around that pitch, and your subsequent response. It sounds like you didn't go forward with implementing that ... was it your decision to not move forward, or were you in a team and that's just what ended up happening?
- derefr 7y agoThe startup that I was working at, that came up with the pitch, fell apart before we ever had to make the call to implement it. Which I’m somewhat glad of; I don’t really like the idea of being forced to choose between ethics and helping a few friends survive. (And don’t get me wrong, building this extension would have been a matter of survival for the startup—we were depending heavily on piecing together a unified social-network graph to do Dynamic Network Analysis to, and social-network services actively resist having this data pulled from them.) If you’re curious, the point of the startup was to path-find between you and people you want to be connected to but aren’t (investors, say), telling you which friends-of-friends to prioritize getting to know in order to later leverage them as intermediate links in the chain to meet the people you really want to meet, that are three or four or five steps removed from you, and so entirely invisible to your local part of the network. (And yes, that’s a really darn cynical play. But the data that we did have showed that the intermediate “links” in your chain would almost always be business-people, “growth hackers”, etc. for whom getting to know you was valuable in its own right—they would value any chance to grow their Rolodex. So it at least seemed like a positive-sum interaction on the surface.)
- deleted 7y ago[deleted]
- dessant 7y agoThe discussed API changes do not limit malware to snoop on browser traffic, requests can still be observed, and scraping is also not affected. Ad blocking is arguably one of the best ways to protect yourself from malware, and that is the capability Google attempts to limit.
- derefr 7y agoAh, alright. Too bad, actually; I was hoping there was a silver lining. Well, maybe—did the API previously give extensions the ability to rewrite the request in-flight? Such as e.g. to rewrite Amazon requests to embed the extension-author’s Amazon affiliate ID? I know extensions can do that, but I’m not sure how they accomplish it; it’d be nice if that could be quashed. But really, you shouldn’t be equivocating the particular capabilities this API provides with the ability to block ads altogether. There are many ways to implement ad blocking, and not all of them require the capability to have your extension active “on the wire”, intercepting network traffic and doing arbitrary Turing-complete things in response with full extension-level capabilities. Personally, from my perspective (and Google might share this perspective), this API was never “the ad-blocking API.” A true “ad-blocking API”—a single-purpose one that can’t be used for any other malicious purpose—is the thing Safari has, where your extension can feed a block list into the browser, and the browser will prevent network requests matching the block list itself, without ever informing your extension that it has done so. Of course, Google would never implement that API in Chrome. And that’s the real problem. I don’t blame Google for limiting some other API that isn’t really “about” ad-blocking, but which can be used to block ads as a side-effect; just like I don’t blame Intel for making their processors slower in response to Spectre/Meltdown. Sometimes security for users trumps useful features or performance. But I certainly do blame Google for not implementing an API that has absolutely no security impact—is perfectly safe, perfectly performant—and blocks ads. If anything has ever been decreed on-high from Alphabet to the Chrome team, it’s likely “don’t implement the Safari content-blocking API, or any standard based on it.” Not anything to do with this API. This API is just problematic, and the Chrome team themselves want its capabilities out of the hands of extension authors.
- dessant 7y ago
- dotancohen 7y agoCan confirm that using users for social media scraping is huge. I worked in that field for some time, though the product was never brought to production. Note that in our case, though, the user was completely informed that they were acting as a node in a network. They provide the ability for us to collect non-public data on other users, we provide them with non-public data on other users that they do not have access to.
- rsync 7y ago"They provide the ability for us to collect non-public data on other users, we provide them with non-public data on other users that they do not have access to." Really doing God's own work there ...
- dotancohen 7y agoOh, we knew it to be the devil's work. The idea was to gauge how much people are willing to share, in order to get something that they want. It was disgusting just how many people were willing. Far from a technology demonstrator, it was a social contracts demonstrator. Most people have no morals and will happily turn over their "friends'" personal information. Just look at how many Android apps require the Contacts permissions.
- creato 7y agoSo, do the new API changes block people like what you were working on? Because I sure as hell hope they do, and if the changes mean ad blockers have to adapt, so be it.
- AlexandrB 7y agoI don't think they do. > In Manifest V3, we will strive to limit the blocking version of webRequest, potentially removing blocking options from most events (making them observational only). Content blockers should instead use declarativeNetRequest (see below). [1] https://docs.google.com/document/d/1nPu6Wy4LWR66EFLeYInl3NzzhHzc-qnk4w4PX-0XMw8/edit# https://docs.google.com/document/d/1nPu6Wy4LWR66EFLeYInl3Nzz...
- the8472 7y agoThat argument generalizes to not allowing users to have any say and to trust big brother knowing what's best for you instead.