Hacker News new | ask | show | jobs
by ShinTakuya 2097 days ago
Blocking users who block ads is no different to blocking users who don't have a premium account. Viewing ads is just a method of payment. In an ideal world all information would be free to everyone, but servers cost money. One way or another, servers need to be paid for. Donation models often allow for the most free distribution of info such as for Wikipedia. But it doesn't work for all cases. And in those cases, ads are often a good solution, since the information is still basically free. If you don't want to pay, that's fine. You can always visit another site that doesn't force payment.

Edit: Just to be clear, I'm actually not against ad blocking. In fact, I use an ad blocker myself. I just think it's hypocritical to expect it to be okay to block ads without also accepting that sites can choose not to serve you (sometimes at their own business peril).

1 comments

False, on facts and law too: DMCA defines "effective access control mechanism" (paywall) and browsers can't hack through those. Anyone who does by exploiting server-side vulns gets in big trouble.

Ad blocking is not like paywall circumvention. Ad and (what Brave does, don't misdirect or let others who get paid to whitelist ads while not blocking trackers, notably Eyeo who owns AdBlock Plus) tracker blocking is allowed by design of the Web standards, and entails no effective access control mechanism to circumvent.

Script blocking in general is a good idea. Signed, creator of JS.

Hello CEO of Brave, I didn't say that blocking ads is the same as circumventing paywalls. I said argued (in essence) that blocking users who block ads is a form of access control. I affirmed that people have the right to block ads, but I also asserted my argument that the owner of a server should have the right to block their access if a user tries to access their content without respecting the terms of access.

Signed, an average developer.

“Blocking users who block ads is no different to blocking users who don't have a premium account.”

I get what you mean: either side of the protocol can do what it wants. Also that the publisher has to cover costs via ads or some kind of payment for content, if they aren’t compensated otherwise (separate business on the side; donations).

But your wording was too broad, as it equates (“no different”) blocking content in browsers, which is allowed by design of web standards for accessibility and any reason the user wishes, and blocking via a server side subscription paywall.

Yeah I can live with accepting that my wording was too broad. I think ultimately we agree to some extent, I can admit some fault for not being clear in my wording. All I was arguing is that we shouldn't be arguing in support of ad blockers only to cry foul when publishers want to block the freeloaders. Although wanting the browser to do it on their behalf is a bit much, I can agree.