I don’t get it, this stuff is already behind a paywall already. There’s no darkening of the internet of news if news is already paywalled. Looks like false controversy to me. All publishers have to do is demand a login and that’s it. Articles that are now behind a paywall will continue to do so. There’s no difference that I can understand outside of a slight adjustment in paywall protection. Seriously can anyone expl…
Google unlocks 33% of publisher paywalls on July 30
11–20 of 229 posts
Re: Google unlocks 33% of publisher paywalls on July 30
#12I don’t get it, this stuff is already behind a paywall already. There’s no darkening of the internet of news if news is already paywalled. Looks like false controversy to me. All publishers have to do is demand a login and that’s it. Articles that are now behind a paywall will continue to do so. There’s no difference that I can understand outside of a slight adjustment in paywall protection. Seriously can anyone expl…
Purely anecdotally, I never remember seeing the "Incognito walls" before a year or so ago; paywalls are clearly able to function even if they can't stop the use of private modes.
Many/most paywalls can be bypassed by blocking or wiping cookies. I wonder if news sites are going to come for cookie blocking next.
Re: Google unlocks 33% of publisher paywalls on July 30
#13Re: Google unlocks 33% of publisher paywalls on July 30
#14No. This isn't about Google unlocking paywalls. This is about Google fixing a bug where the presence of Icognito Mode could be detected with JS which is totally against the premise of Incognito Mode whose purpose it is to be undetected, not to be detected as somebody wanting to be undetected. Publishers can everybody to be logged in in order to read their content. Then none of this applies.
This is part of the articles point. Forcing people to login is going to hurt conversion.
Re: Google unlocks 33% of publisher paywalls on July 30
#15Hard paywalls will just make even less people to read sites like nyt, wp, wsj and their revenue will probably go even down.
subscribe to read? no way. my modus operandi is that if I get to a link and it asks for a login or to subscribe, I just close the tab. there's a few websites that I don't even click anymore because of that.. and the list just keeps growing to me.
Re: Google unlocks 33% of publisher paywalls on July 30
#16I feel for sites that provide a service that want to bring users in, and still offer them some content up front for free. Having said that as a user I should be able to be anonymous at will too...
But anecdotally, news orgs will never get my money while their subscription terms continue to be asinine. I will gladly give a newspaper $25 - $50 a year for access. I will not play these $X/week for odd week increment games.
Re: Google unlocks 33% of publisher paywalls on July 30
#17NYT already blocks you from reading articles when you’re in incognito.
hmm this is exactly what the update will prevent...
Re: Google unlocks 33% of publisher paywalls on July 30
#18Re: Google unlocks 33% of publisher paywalls on July 30
#19There are going to be people complaining about the new requirement to have an account to view content. To the publishers, you should _really_ use some kind of federated login. Google, Apple, Facebook, etc. but don't forget those who are willing to have a unique account.
Re: Google unlocks 33% of publisher paywalls on July 30
#20I don’t get it, this stuff is already behind a paywall already. There’s no darkening of the internet of news if news is already paywalled. Looks like false controversy to me. All publishers have to do is demand a login and that’s it. Articles that are now behind a paywall will continue to do so. There’s no difference that I can understand outside of a slight adjustment in paywall protection. Seriously can anyone expl…
They've been using soft paywalls which allow people to read a certain number of articles per month for free. To prevent users from simply using incognito mode to pretend every visit is their first visit, publishers started detecting incognito mode and blocking them from reading articles using it (without signing in).
Now we'll see what their response is, probably something moronic as 5 views per IP.
Better to just require an account straight up. Then there is no point for anyone to link to them and we will get rid of the whole "will I be able to read this link mess".