Care to expand on that?
Care to expand on that?
In effect ABP was forcing itself in as a middle man and taking a fee from both the site owner and the advertiser. As an example, if I, your local newspaper, sell a placement to your local car dealership, ABP comes in and says "people won't see the car ads, but if you split the revenue you were going to get with me, I'll sell those placements to someone else for you." So let's say 10% of my visitors use ABP. I can now either lose it or get back some smaller percentage of it by paying ABP.
That's one DDoS short of a digital protection racket.
In addition, when Eeyo made that announcement, they also announced that they were working with AppNexus and Google on the new exchange, which just wasn't true. Though I believe Google does pay to get some ads into the acceptable ads program.
If you're going to be in the business of blocking ads, stay out of the business of selling ads.
Your specific condemnation rests on this tired narrative that "ad spots" are something belonging to the site owner. In the reality of the web, it's all the user's display area - the user agent decides what and how to render.
The real critique is that the software is working against the user's interest for its own gain. This is par for the course of proprietary software, but generally seen as unsustainable poor taste in the Free world. Fortunately, having achieved the activation energy of installing extensions for one's self, switching is not hard.
I'm willing to concede that I assume a specific view of the nature of ad spots, but you're going to have to reeeeeeaaaaally stretch your argument to claim that this is the reality of the web. For the vast majority of people the browser is the renderer that happens to be customizable, not the arbiter of what is rendered, regardless of the browser's capability to decide.
Regardless, you don't have to accept the online advertising business model, even at a moral level, to acknowledge the shadiness of the other aspects of the practice that I pointed out.
It felt that way to advertisers especially when the fee was 30% of ad revenue rather than say, a processing fee for time spent verifying it met the criteria. A lot of them were more ok to ignore ad blocking before they were held to ransom.
Users were unhappy at an adblocker's default config allowing ads.
A feature being able to be turned off is a plus, but default features not in the interest of the user are a minus. Especially not when users don't have an easy way to opt-out.
If users reasonably want to only opt-in such a feature, you as developer should implement it as such.
When I first heard about it took me like 35 seconds to opt-out -- open options and unclick the little clicky box, easy peasy.
Having to go through settings in software when you install it, to get the software to work the way the average user wants it to, is annoying. An example could be removing a bitcoin miner from the software, or disabling ads in uTorrent, or disabling telemetry in Windows 10. Firefox as well, but at least they tell you about it right away, and they started doing it later. Not good, but less bad.
Why do software developers get away treating their customers like stupid sheep either wasting their time or getting their data? Ah well, at least in Europe we're getting GDPR.
It's not like they owe me anything, I downloaded their software for free and use it for free with absolutely no expectation other than "I'll use it as long as it works for me."
If it gets annoying I'll replace it with something that isn't just in this particular case it was a lot easier to click a box than search out a new adblocker.
> Why do software developers get away treating their customers like stupid sheep either wasting their time or getting their data?
Because they want to use Windows 10 or uTorrent or something with a bitcoin miner instead of searching out alternatives. Personally, other than ABP, I can think of no other cases of this happening on my stock (other than the chrome repo) Fedora box.
Glad we're getting GDPR in EU. I hope other countries like USA will follow suit. US citizens deserve such protection just as much as EU citizens. Not to mention the rest of the world. We'll have to see how it works out in practice though.
As for the owing and such regarding FOSS, that's related to warranty and such. That doesn't mean its cool to deliver the software crippled. Especially not without mentioning it is crippled beforehand. We got a word for that in the physical world: dishonesty.
Which is why you should use some due diligence before (and after) choosing which products you use. It's not like anyone's forcing you to sell your soul so you can find out your best friend's dog Fluffy just went to the groomers and here's the pictures.
I see this like those people who go and buy a house next to an airport then go crazy complaining to the city about airplane noise, they benefit from cheaper prices (because most people don't actually want to live next to an airport) but then feel entitled enough to feel everyone else should bend over backwards for their personal preferences.
> Glad we're getting GDPR in EU...We'll have to see how it works out in practice though.
Produce a digital wasteland IMHO...like the tariff wars that (partly) led up to the Great Depression.
In the previous century I did not expect any tool to send back data about usage (including my private data). Back then it was called phoning home [1]. It was very much frowned upon. Although, as the internet took off, it started to become more rampant as a way to verify software. For example, I remember a personal firewall trying to phone home to verify it was licensed which you could block with... itself. Later they fixed that, but you could just use a hex editor to fix that.
Nowadays we've migrated from pay to use model (proprietary software) to service for your privacy model (SaaS). We get disillusioned that things are free when in reality they're not. In the physical world, but more so in the digital world. We don't know how we are paying, and that's a problem. [2]
> I see this like those people who go and buy a house next to an airport then go crazy complaining to the city about airplane noise, they benefit from cheaper prices (because most people don't actually want to live next to an airport) but then feel entitled enough to feel everyone else should bend over backwards for their personal preferences.
No, those people knew beforehand what they were buying. We don't, else we'd change those settings right away. Claiming that people consent to their privacy being discarded is dishonest. They don't fully understand the effect of their actions. The developers do know, but they don't care, maybe cause they're aspies who can keep distance from that --I'm not sure.
As for people who live near an airport, I happen to know a tad bit more about that with regards to the airport near Amsterdam (I live near Amsterdam). It all depends on the flight routes (the lanes for landing and take off). For example, I don't hear any airplanes except in the summer because then that specific route is used more. Not every 15 minutes though like my aunt who lives a few km from one lane in the Green Heart on a boat with a beautiful land. With, during the summer (winter etc less), planes going over. Low. Every. 15. Minutes. It would drive me nuts.
> Produce a digital wasteland IMHO...like the tariff wars that (partly) led up to the Great Depression.
How so? Look back at what I wrote here [2]. Don't you think the GDPR will make it very transparent to users because they have to give their consent?
[1] https://en.wikipedia.org/wiki/Phoning_home
[2] See other [2]
Not only the software developers and to why? Well because it works, because most act like sheep.
I wonder how much of that comes from having been dominated for century's by a religion who literally told (and tell) all the people that they are sheep, needings them as shepherds ...