799 karma · joined February 5, 2009
All nice in theory... the real world is very different.
Note you can only block 500 sites, I should think thats enough though.
So can I disable the chrome plugin now? Will it remember the sites I have already blocked?
So you have to install and manage your own local ad server to earn ad revenue from your site? Many publishers large and small use ad servers e.g. doubleclick, adtech to avoid this overhead.
>Why can't the advertisers simply re-evaluate the rates they pay per impression based on the expected cost/benefit under the new model?
Yes, publishers loose out once again.
I think thats a key point. ALL banner advertising would be affected by this change. All ad servers use cross domain cookie tracking of some kind. If not to track user behaviour, its (for example) to track impressions to make sure that you dont show the same ad to the same user more than a set number of times. That is also a 3rd party cookie.
Without that ability it will be hard (impossible?) to rate limit campaigns to users, thus increasing the cost effectiveness to the advertiser and eventually hurting publishers as advertising money is diverted elsewhere.
In short, this rule would affect ALL banner adverts on all sites. So 99%, yes (at least the content sites I have read today).
Me and 99% of the sites I have read today...
> The most lucrative advertising deals I know about are between sites catering to particular interest groups and advertisers
In my experience, the most lucrative advertising campaigns are based on audience tracking and retargeting.
It also gives flexibility back to site owners. If you business model depends on tracking (so much that a visitor who opts out of tracking costs you money) they are free to redirect the user away or throw up a paywall.
It only really falls down when there are a large number of totally identical machines in the same IP range, where the machines are locked down so plugins (etc..) cannot be installed. E.g. a large office or university lab.
Advertising is the life-blood of publishers on the Internet. Without advertising (and by extension, tracking) many of the sites you enjoy every day would cease to exist.
At least using cookies you CAN opt out (via browsing settings and plugins). All that will happen is that the tracking networks will switch to browser fingerprinting making tracking harder to control and more opaque.
Also, just because a feature is offered 'as a gift' does not mean it should automatically be included in a OSS project. Thats how projects become bloated (this is not comment for or against the idea, just a general point).
Trust me, use a 3rd party service.
Does not need to be mail chimp though. I am using these guys:
Crappy site, but good server. Just a well set up SMTP server, so with a few config lines from your app you can send mails through this instead of your own server.
So, when if I install this extension, I can hack those files (in the extension's directory I assume) reload the browser and the javascript engine will do whatever I have changed?
My understanding is that its an alternative javascript engine that can be modified (using javascript itself I assume) and those modifications packaged and shared.
Is that right? I was looking for an example of how you modify the engine and what can be modified. Any ideas?