Some Internet sites make use of a safe mode to filter out objectionable contents. This is true for search engines such as Google Search, Startpage or Bing, or video sites like YouTube.
When enabled, contents with adult themes may be filtered out automatically by sites. The safe mode is usually set to a moderate level so that select contents get filtered out while others don't.
One issue that arises out of this is that it is difficult to make modifications. It is not only necessary to make sure the mode is correctly configured for each site and browser used, but also for each account on the system.
The Safe Preference header aims to simplify this approach not only when it comes to configuration, but also in terms of automation.
The request is added to the user agent that gets transferred automatically when websites or services are accessed on computer systems.
If the safe preference is included in the user agent, websites can use it to set safe mode filters automatically.
How it is set up
If you analyze the effectiveness of the new preference, you will notice two core issues. First, it is only supported by Firefox and Internet Explorer. If a user switches to another browser that is not supporting the preference, it won't be effective at all.
The second issue is that websites need to support it. If no website or only select ones support it, it is not helping at all on websites that do not.
Mozilla has not mentioned which versions of Firefox support the Prefer:Safe preference while Microsoft has added it to Internet Explorer 10 and 11 only. Update: Mozilla has integrated it into Firefox 31.
Internet Explorer users need to make sure that this update is installed on the system.
It is unclear how successful the Safe Preference will be. It has been submitted as a draft to the Network Working Group. On the plus side, it is implemented by Internet Explorer and Firefox which together hold a sizable browser market share.
Including safe in the header does not necessarily mean that only safe contents will be displayed to users of the browser. As mentioned earlier, if a site does not support it, it may display unsafe contents to the user by default or filter only some contents but not all.
There is also fingerprinting to consider as sending the information add one information bit to the fingerprint.
Will it be successful? It depends a lot on Google and whether the company will implement it in its Chrome browser. Last but not least, it is also of importance that websites implement it as it has no meaning otherwise.
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.