![\"chrome](\"https:\/\/daily.net\/wp-content\/uploads\/2011\/08\/chrome-Web-Store.png\")
<\/a><\/p>\nChrome extensions are meant to be clean and simple. Google is even making a move to ban obtrusive extensions<\/a>, because sometimes these can harm your Chrome experience. There is another recent threat Google is dealing with, though. Companies have been acquiring extensions from developers in order to turn them into adware clients. <\/p>\n Google has banned a couple of these extensions: Add to Feedly and Tweet this Page. These were once awesome extensions that helped users get the most out of the Chrome browser. They served a purpose. How did it all go downhill? Did the developers get greedy? Not at all! <\/p>\n In Add to Feedly’s case, the original developer was Amit Agarwal. Said developer was offered “a four digit” amount for his extension, which only took about an hour to code. Of course, he accepted and the transaction went smoothly. He regretted his decision when the new owner pushed an update to the extension, though. <\/p>\n The new owner turned his helpful extension into an ad-serving machine. These were not regular ads either, they worked in the background and replaced links on every website! Original links were replaced by affiliate links without anyone’s knowledge. <\/p>\n It’s very sad to see people trying to take advantage of good products. Google’s new policies will help make this all better, though. Soon we will not have to worry about all those spammy extensions. <\/p>\n [Ars Tecnica<\/a>, labnol<\/a>]<\/p>\n","protected":false},"excerpt":{"rendered":" Chrome extensions are meant to be simple and single-purposed tools, but some adware has become a problem. Companies have been purchasing and ruining helpful extensions. <\/p>\n","protected":false},"author":4,"featured_media":4566,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"xf_promoted_thread_id":0},"categories":[10],"tags":[138,226,311,397,31,3190,1252],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/daily.net\/wp-json\/wp\/v2\/posts\/5286"}],"collection":[{"href":"https:\/\/daily.net\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/daily.net\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/daily.net\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/daily.net\/wp-json\/wp\/v2\/comments?post=5286"}],"version-history":[{"count":1,"href":"https:\/\/daily.net\/wp-json\/wp\/v2\/posts\/5286\/revisions"}],"predecessor-version":[{"id":53909,"href":"https:\/\/daily.net\/wp-json\/wp\/v2\/posts\/5286\/revisions\/53909"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/daily.net\/wp-json\/wp\/v2\/media\/4566"}],"wp:attachment":[{"href":"https:\/\/daily.net\/wp-json\/wp\/v2\/media?parent=5286"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/daily.net\/wp-json\/wp\/v2\/categories?post=5286"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/daily.net\/wp-json\/wp\/v2\/tags?post=5286"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Why Google banned the extensions<\/h2>\n
Was it the developer’s fault? Not exactly!<\/h2>\n
<\/a><\/p>\n