Strict Standards: Only variables should be assigned by reference in /home/noahjames7/public_html/modules/mod_flexi_customcode/tmpl/default.php on line 24

Strict Standards: Non-static method modFlexiCustomCode::parsePHPviaFile() should not be called statically in /home/noahjames7/public_html/modules/mod_flexi_customcode/tmpl/default.php on line 54

Strict Standards: Only variables should be assigned by reference in /home/noahjames7/public_html/components/com_grid/GridBuilder.php on line 29
Firefox-maker Mozilla devises three laws for responsible ad blocking

Online content blocking is a hot topic thanks to Safari Content Blockers in iOS 9 and the recent news around AdBlock and AdBlock Plus. Now Mozilla is jumping into the issue with a set of guidelines the Firefox-maker will use, and hopes others will adopt, in deciding when and how to apply the banhammer to online content.

Mozilla is proposing three basic principles: content neutrality, transparency and control, and openness.

The first principle means content blocking software should block content based on user needs and not just because it’s a specific type of content. In other words, if an ad isn’t violating user privacy or security it shouldn’t be blocked, similarly to how the EFF's Privacy Badger extension behaves.

Transparency and control says that users should have the final say on how to control their experience and be able whitelist certain components of a site (or an entire site) as they see fit.

Finally, openness means content providers, such as site owners and advertising companies, should be allowed to interact with content blocking systems. That way if a particular behavior results in an advertiser being blacklisted there will be a mechanism in place to return to the good graces of a content blocker.

Mozilla’s new guidelines are really nothing new and you can find some or all of these principles at work with other organizations, services, and products. The Firefox add-on NoScript, for example, offers users detailed control over what does and does not get blocked on a particular site.

Mozilla says these new guidelines, which you can read on the organization’s blog, are only a first draft and it wants users to participate in the discussion. Mozilla will be watching the #contentblocking hashtag on social networks to see what people have to say. On Friday, October 9 at 11 a.m. Pacific/2 p.m. Eastern, Mozilla will also host a Twitter chat using the hashtag #BlockParty to discuss content blocking issues.

The story behind the story: Privacy and ads have been a big focus for Mozilla in recent months. In mid-September, the Firefox maker introduced its own targeted ads with minimal and aggregate user tracking on Firefox’s new tab page. Mozilla’s ads are an experiment to find supplemental methods of funding beyond the default search provider deal it has with Yahoo. More recently, Firefox Beta rolled out a true stealth mode called Tracking Protection that is, in effect, a content blocker preventing third-party tracking when in private browsing mode.

Read more http://www.macworld.com/article/2990430/browsers/firefox-maker-mozilla-devises-three-laws-for-responsible-ad-blocking.html#tk.rss_all


Strict Standards: Only variables should be assigned by reference in /home/noahjames7/public_html/modules/mod_flexi_customcode/tmpl/default.php on line 24

Strict Standards: Non-static method modFlexiCustomCode::parsePHPviaFile() should not be called statically in /home/noahjames7/public_html/modules/mod_flexi_customcode/tmpl/default.php on line 54

Find out more by searching for it!

Custom Search







Strict Standards: Non-static method modBtFloaterHelper::fetchHead() should not be called statically in /home/noahjames7/public_html/modules/mod_bt_floater/mod_bt_floater.php on line 21