4 ms·
Who is actually calling the shots over at Google? In January, Google announced that Chrome was going to be blocking all ads on domains that had too many ads (
by AJ007 7y ago
Who is actually calling the shots over at Google?
In January, Google announced that Chrome was going to be blocking all ads on domains that had too many ads ( https://blog.chromium.org/2019/01/building-better-world-wide-web.html https://blog.chromium.org/2019/01/building-better-world-wide... ) ; website owners were told to use the new "Ad Experience Report" in Webmaster Tools/Search Console to find out if they passed our not. Months later, my sites never were reviewed. Everyone I asked also did not have their sites reviewed.
Now Google has updated the Search Console and this "Ad Experience Report" is no where to be seen.
Maybe whoever came up with this idea and announced it never had the authorization to do so. After all, Google's Adsense was happily encouraging web site owners to add ad placements to their websites that were blatant violations of these new rules, including the most egregious, full page interstitials. The UI of Adsense would easily convince a more novice operator to just turn on "auto ads" and have Google blanket their website with ads automatically. Certainly this couldn't have been the plan, follow Google's advice so that your site could never earn advertising revenue from Chrome users again?
I suspect Google does have a plan to deal with ad blocking. They might have a few plans. Right now, it resembles someone bashing their own head against a wall. These changes to Chrome precipitate the end of Chrome having a dominate desktop market-share. If it really happens. But no matter what happens, Google is once again a little less trustworthy after.
- fauigerzigerk 7y ago>Who is actually calling the shots over at Google? I think there was a guy whose 20% project was calling the shots but he eventually replaced himself with a GAN or something.
- detaro 7y agoIt's a big company, it's not unlikely that different parts follow different, conflicting plans.
- magashna 7y agoGoogle loves to get 40% into a project and then run away like chickens with their heads cut off
- kretor 7y agoChrome security lead Justin Schuh says he is responsible: "The sole motivation here is correcting major privacy and security deficiencies in the current system. I know, because I set that focus, and the team reports up through me." https://twitter.com/justinschuh/status/1134092257190064128?s=20 https://twitter.com/justinschuh/status/1134092257190064128?s...
- jzl 7y agoUgh. Reading this guy's account is just making me depressed. There is not a single convincing or meaningful response to gorhill's excellent and concise twitter thread: https://twitter.com/gorhill/status/1134127701583904770 https://twitter.com/gorhill/status/1134127701583904770 All I see is handwavy posturing and tweets like this: "I should know better than to check Twitter after a painfully long day, but I am not dumb enough to actually reply to any of this crap." This is the person who (by his own claim) is making the call on something that will fundamentally change the entire Internet?
- elliottkember 7y agoThe same person who made these incredibly snide comments on the Chrome password debacle a few years back: https://news.ycombinator.com/item?id=6165708 https://news.ycombinator.com/item?id=6165708 https://news.ycombinator.com/item?id=6166953 https://news.ycombinator.com/item?id=6166953
- shawnz 7y agoTotal nonsense. In the manifest document it claims that the change is for performance reasons, not privacy/security. Is it for performance, or privacy/security as he says? If it's the latter, then why aren't they deprecating the observational parts of the webRequest API?