You are currently browsing comments. If you would like to return to the full story, you can read the full entry here: “If you are on Chrome, it won’t let you see this”.
You are currently browsing comments. If you would like to return to the full story, you can read the full entry here: “If you are on Chrome, it won’t let you see this”.
I’m sure this is probably very ironic but, given your views on Google, are you aware that, by using blogroll, you’re adding Google Analytics tracking code to all your pages?
I had no idea. In that case, it’ll have to go. I’ll just have to take the time to import each entry into the WordPress blogroll instead of the Blogrolling one.
Um, using Chrome and can see this … am I missing something?
Um (2) – did a Google search for this post (http://www.google.co.nz/search?sourceid=chrome&ie=UTF-8&q=If+you+are+on+Chrome,+it+won%E2%80%99t+let+you+see+this) and there it is, first item.
I used a Chrome Incognito window so not logged in.
Same with Firefox (again, not logged into Google): http://www.google.com/search?client=ubuntu&channel=fs&q=If+you+are+on+Chrome%2C+it+won%E2%80%99t+let+you+see+this&ie=utf-8&oe=utf-8
All on Ubuntu.
Sorry Jack, not seeing what the issue is
Mike, that is easily explained: at 4.30 p.m. today, after Andrew’s comment about Google Analytics, I removed the old blogroll and replaced it with a Wordpress one.
Um, be surprised if it’s the Blogrolling service though – can visit the site in Chrome and all good.
I think you’re commenter (on your blog) was referring to the fact that you were having Google Analytics ‘inserted’ into your site by Blogrolling and not that it was causing your site to be marked as ploppy-poos
But I could be wrong, the Web is a weird and amorphous beast
A Tweeter sent me his screen shot and it pointed at two links that one could have arrived at through Blogrolling—but not my blogroll. That seemed to be the reason for Chrome’s decision to block this blog. If I can find his Tweet to me, I’ll paste the URL, as there might be an alternative explanation.
You are correct: Andrew was not suggesting that Analytics was causing Chrome to mark my site. He simply found it ironic that I would be Google-sceptic yet allowed a blogroll service that inserted Analytics code.
Dan Satherley to me on Twitter got this from his Chrome: ‘The website at jackyan.com contains elements from the site rpc.blogrolling.com, which appears to host malware.’ So perhaps it is the rpc subdomain and not www? Still hunting for the screen shot.
What’s about chromium-browser, its free and not Google (Google take the source for his Chrome). I use it with Linux and with DDG ;)
I also will start to kick Google off. For website analytics I use the very useful Piwik. [http://duckduckgo.com/?q=piwik → Zero-click]
Tim, thank you. I tried Chromium but it interpreted some HTML code in a non-standard way. Glad to meet another DDG fan!