Just a quickie before diving into 2011;
- I’m having great fun with jQuery and a templating plugin called jQote2. Not getting into specifics or examples yet, but if you’re into jQuery jQote2 is well worth checking out!
- I’ve created a small plugin, DoNotTrack, to stop the Quantcast tracking that e.g. the WordPress.com Stats plugin introduces. You can download it here to give it a try. If time & my brain permit, this plugin could become a general solution to stop any unwanted tracking by other plugins on your blog.
- There’s a new version of WP YouTube Lyte with some small fixes & tested on WordPress 3.1 RC. We’re rapidly approaching 10.000 downloads, a great way to start a new year!
And this is how I feel about 2011:
Have a great New Year!
Just wanted to say ‘thanks’ for releasing the DoNotTrack plugin!
Much thanks for the plugin to stop the Quantcast tracking script. I am sending good Karma your way!
Thanks for the DoNotTrack plugin! I’m testing it on my second blog now, and it seems to work fine blocking Quantserve so far.
However, it breaks some existing, “good” document.write by making every written text lower-case. My quick solution was to replace the beginning of function sanitizer in the JS file with
tSL=tS.toLowerCase(); if((tSL.indexOf(unescape('%3Cscript'))!=-1)&&(tSL.indexOf(unescape('src='))!=-1)) {for(x in spy){if(tSL.indexOf(spy[x])!=-1){
(and leave the rest unchanged), i.e. use the toLowerCase result (in tSL) only for comparison, but not for modification and output.Also, do you think it’s okay to include this short Javascript inline in the header, instead of in a separate file? This would remove this additional HTTP request to load the .js file.
thanks for the feedback, i’ll look into this!
ok, solved the lower-case bug the way you did. I didn’t move it inline yet though, why would you prefer that?
the new version (0.1.1) is on the same URL (http://futtta.be/donottrack.zip).
To be nitpicking, you got one difference: you’re assigning the lower-cased modified version to the output with
tS=ttS.replace(...)
– but that doesn’t really matter since it only affects additional text that’s written together with an offending tracking script in the same document.write command, and everything will be fine for “good” document.writes. 🙂Putting it inline: well, the fewer external files the browser has to load, the faster the page will be loaded – though there won’t be much difference here with this small file, I guess, and it’s still faster than the Quantcast file(s).
it’s correct that loading less external (js- and css-) files is recommandable, and in general there are a lot of js/css-files that are included by plugins (including mine, I admit). That’s why I use the CSS/JS booster plugin (made in Germany) to move all CSS and all JS into one file each. Great plugin, really!
Many thanks for donottrack – good to know the wordpress community is still classy and ready to step in when needed.
Ok I want to include the tracking but only remove the call for the pixel, is this possible? to get rid of this error
“pixel.quantserve.com/pixel…..
Resource interpreted as Image but transferred with MIME type text/plain.”
i’m afraid not john; as far as I know the tracking is done with the pixel. Just curious; what browser do you use to complain about mime-types?
Hi Frank, I use Google Chrome to develop and debug
Hi Frank, thanks for this awesome script.
Today I visited my site without being logged in and noticed that something was loading from pixel.quantserve.com again and it was really slow (As in won’t load at all).
It looks like the WP.com Stats script got updated and no longer uses document.write to insert the Quantcast script. It uses an asynchronous method now. Therefore, the notrack script doesn’t seem to work properly anymore.
It still uses document.write to insert the Stats smiley though…
indeed 🙁
guess i’ll have to start digging for a better solution then.
i’ve got a new version of donottrack (details to follow in a blogpost one of the following days) that stops the new quantcast-code from working. you can download it here.
Hlw sir it works like a charm. But i have an issue with it. After installed ur plugin my site page loading speed got down a bit.
Before install:-
According to gtmetrix com my site
Page Speed Grade: (A) 99%
YSlow Grade: (A) 92%
After install:-
Page Speed Grade: (A) 95%
YSlow Grade: (A) 93%
My page loading speed got down 4% while YSlow Grade got up 1%. Which made me upset. Is there any solution for me?
So what do you think about it. Waiting for ur response.
I you check out http://gtmetrix.com/compare/MpKVTXQA/CJxczTrR, you can see the main differences between your site without (first) and with (second) WP DoNotTrack are:
1. for pagespeed:
Optimize the order of styles and scripts A (100) B (85)
Remove query strings from static resources A (100) A (90)
2. for yslow:
Add Expires headers D (67) B (89)
Put JavaScript at bottom A (100) A (95)
3. for timeline:
12 Requests 19.9 KB 542ms (onload: 549ms)
11 Requests 19.4 KB 425ms (onload: 429ms)
So:
Short and to the point: thanks so much for the “do not track” plugin.
lisbeth
Thanks for this Wonderful Plugin! #DoNotTrack