<\/p>\n
Credit to Author: John E Dunn| Date: Mon, 22 Jul 2019 13:24:56 +0000<\/strong><\/p>\n\n\n \t\t\t\t \t \t\t\t\t\tby<\/span> \t\t\tJohn E Dunn<\/a>\t\t \t \t\t\t\t<\/div>\n\n\n<\/use><\/svg><\/a><\/li>\n<\/use><\/svg><\/a><\/li>\n<\/use><\/svg><\/a><\/li>\n<\/use><\/svg><\/a><\/li>\n<\/ul><\/div>\n<\/p><\/div>\nHave you ever bypassed a website paywall using a browser\u2019s privacy mode?<\/p>\nIt used to be a simple hack to read an article without registering, paying, or logging in to the publisher’s website. But subscription-based websites caught on.<\/p>\nNow, for example, visit any article on The Washington Post news site while in Google Chrome\u2019s Incognito mode, and you\u2019ll get the following message:<\/p>\n\nWe noticed you\u2019re browsing in private mode. Private browsing is permitted exclusively for our subscribers. Turn off private browsing to keep reading this story, or subscribe to use this feature, plus get unlimited digital access.<\/p>\n<\/blockquote>\nThis is annoying, not because it means the visitor can\u2019t access the story (the publisher is, of course, within its rights) but because it seems to be imposing restrictions on the whole idea of private browsing.<\/p>\nIf it\u2019s up to publishers to decide when a visitor is allowed to remain private, is that mode really private?<\/p>\nPlans to remedy the loophole<\/h2>\nAs we reported earlier this year,<\/a> Google agrees and has laid out its plans<\/a> to \u201cremedy the loophole\u201d websites have been using to detect visitors using Chrome\u2019s Incognito mode.<\/p>\nThe loophole in question is Chrome\u2019s FileSystem API, which is disengaged in Incognito mode to keep people\u2019s browsing activity private. Eventually, websites twigged that receiving an error message when checking whether this was accessible was a simple giveaway that visitors had gone Incognito.<\/p>\nThis doesn’t matter to sites that have \u2018hard\u2019 paywalls because a login is required regardless of browsing mode. The issue arises on sites that try to whet readers\u2019 appetites by offering two or three free articles, which means they need to plug ways of beating this limit.<\/p>\nAccording to Google<\/a>, starting with Chrome version 76 on 30 July 2019, publishers will no longer be able to detect Incognito mode by checking the FileSystem API. And just in case publishers look for other methods – the FileSystem API being far from the only giveaway – Google warns:<\/p>\n\nChrome will likewise work to remedy any other current or future means of Incognito Mode detection.<\/p>\n<\/blockquote>\nThe company\u2019s advice to publishers is to adjust their settings to allow more or fewer free articles, or to ask users to log in – something that\u2019s likely to have paywall site owners muttering under their breath.<\/p>\n
Have you ever bypassed a website paywall using a browser\u2019s privacy mode?<\/p>\n
It used to be a simple hack to read an article without registering, paying, or logging in to the publisher’s website. But subscription-based websites caught on.<\/p>\n
Now, for example, visit any article on The Washington Post news site while in Google Chrome\u2019s Incognito mode, and you\u2019ll get the following message:<\/p>\n
\nWe noticed you\u2019re browsing in private mode. Private browsing is permitted exclusively for our subscribers. Turn off private browsing to keep reading this story, or subscribe to use this feature, plus get unlimited digital access.<\/p>\n<\/blockquote>\nThis is annoying, not because it means the visitor can\u2019t access the story (the publisher is, of course, within its rights) but because it seems to be imposing restrictions on the whole idea of private browsing.<\/p>\nIf it\u2019s up to publishers to decide when a visitor is allowed to remain private, is that mode really private?<\/p>\nPlans to remedy the loophole<\/h2>\nAs we reported earlier this year,<\/a> Google agrees and has laid out its plans<\/a> to \u201cremedy the loophole\u201d websites have been using to detect visitors using Chrome\u2019s Incognito mode.<\/p>\nThe loophole in question is Chrome\u2019s FileSystem API, which is disengaged in Incognito mode to keep people\u2019s browsing activity private. Eventually, websites twigged that receiving an error message when checking whether this was accessible was a simple giveaway that visitors had gone Incognito.<\/p>\nThis doesn’t matter to sites that have \u2018hard\u2019 paywalls because a login is required regardless of browsing mode. The issue arises on sites that try to whet readers\u2019 appetites by offering two or three free articles, which means they need to plug ways of beating this limit.<\/p>\nAccording to Google<\/a>, starting with Chrome version 76 on 30 July 2019, publishers will no longer be able to detect Incognito mode by checking the FileSystem API. And just in case publishers look for other methods – the FileSystem API being far from the only giveaway – Google warns:<\/p>\n\nChrome will likewise work to remedy any other current or future means of Incognito Mode detection.<\/p>\n<\/blockquote>\nThe company\u2019s advice to publishers is to adjust their settings to allow more or fewer free articles, or to ask users to log in – something that\u2019s likely to have paywall site owners muttering under their breath.<\/p>\n
We noticed you\u2019re browsing in private mode. Private browsing is permitted exclusively for our subscribers. Turn off private browsing to keep reading this story, or subscribe to use this feature, plus get unlimited digital access.<\/p>\n<\/blockquote>\n
This is annoying, not because it means the visitor can\u2019t access the story (the publisher is, of course, within its rights) but because it seems to be imposing restrictions on the whole idea of private browsing.<\/p>\n
If it\u2019s up to publishers to decide when a visitor is allowed to remain private, is that mode really private?<\/p>\n
As we reported earlier this year,<\/a> Google agrees and has laid out its plans<\/a> to \u201cremedy the loophole\u201d websites have been using to detect visitors using Chrome\u2019s Incognito mode.<\/p>\nThe loophole in question is Chrome\u2019s FileSystem API, which is disengaged in Incognito mode to keep people\u2019s browsing activity private. Eventually, websites twigged that receiving an error message when checking whether this was accessible was a simple giveaway that visitors had gone Incognito.<\/p>\nThis doesn’t matter to sites that have \u2018hard\u2019 paywalls because a login is required regardless of browsing mode. The issue arises on sites that try to whet readers\u2019 appetites by offering two or three free articles, which means they need to plug ways of beating this limit.<\/p>\nAccording to Google<\/a>, starting with Chrome version 76 on 30 July 2019, publishers will no longer be able to detect Incognito mode by checking the FileSystem API. And just in case publishers look for other methods – the FileSystem API being far from the only giveaway – Google warns:<\/p>\n\nChrome will likewise work to remedy any other current or future means of Incognito Mode detection.<\/p>\n<\/blockquote>\nThe company\u2019s advice to publishers is to adjust their settings to allow more or fewer free articles, or to ask users to log in – something that\u2019s likely to have paywall site owners muttering under their breath.<\/p>\n
The loophole in question is Chrome\u2019s FileSystem API, which is disengaged in Incognito mode to keep people\u2019s browsing activity private. Eventually, websites twigged that receiving an error message when checking whether this was accessible was a simple giveaway that visitors had gone Incognito.<\/p>\n
This doesn’t matter to sites that have \u2018hard\u2019 paywalls because a login is required regardless of browsing mode. The issue arises on sites that try to whet readers\u2019 appetites by offering two or three free articles, which means they need to plug ways of beating this limit.<\/p>\n
According to Google<\/a>, starting with Chrome version 76 on 30 July 2019, publishers will no longer be able to detect Incognito mode by checking the FileSystem API. And just in case publishers look for other methods – the FileSystem API being far from the only giveaway – Google warns:<\/p>\n\nChrome will likewise work to remedy any other current or future means of Incognito Mode detection.<\/p>\n<\/blockquote>\nThe company\u2019s advice to publishers is to adjust their settings to allow more or fewer free articles, or to ask users to log in – something that\u2019s likely to have paywall site owners muttering under their breath.<\/p>\n
\nChrome will likewise work to remedy any other current or future means of Incognito Mode detection.<\/p>\n<\/blockquote>\nThe company\u2019s advice to publishers is to adjust their settings to allow more or fewer free articles, or to ask users to log in – something that\u2019s likely to have paywall site owners muttering under their breath.<\/p>\n
Chrome will likewise work to remedy any other current or future means of Incognito Mode detection.<\/p>\n<\/blockquote>\n
The company\u2019s advice to publishers is to adjust their settings to allow more or fewer free articles, or to ask users to log in – something that\u2019s likely to have paywall site owners muttering under their breath.<\/p>\n
![](\"https:\/\/sophosnews.files.wordpress.com\/2019\/07\/shutterstock_279059117-compressor.jpg\"\/)
<\/p>\n<\/p>\n