Google delays an all-clear for as long as it possibly can I am told by those in the know that Google takes about five hours to do a review. I have waited 16 now for today’s one. That’s on top of the six days our site has been blacklisted and libellous things written about us, just because Google cannot distinguish clean code from malicious code. (We know it can’t, since it makes malicious code anyway.)
Colleen Corby gay gibson 1969 by AngoraSox on Flickr.
Gay Gibson Reblogging for the type. Modernism and neo-grotesques are cool.
(via rechercher)
Source: excitingsounds
One out of eight is a majority in Google-land Here’s how Lucire looks via Sucuri, referred by a friend of mine. Given that Google is the only one that thinks we’re dodgy, why on earth do so many sites rely on it, when seven others think we’re fine?
Bit hard to prove I’d love to show you the Badware Busters forum and how Dr Anirban Banerjee of Stopthehacker.com told me how Google messes up with its detection of malware. Unfortunately, as of today, that has gone, too.
SNAFU Google: SNAFU. There are no new pages picked up by its bot as having problems (although we have been clean since Saturday so it has been misclassifying clean code for malicious for nearly a week), and Stop Badware has cleared us of any issues, but it wishes to continue playing its game. It’s the usual, corrupt, damaging behaviour from Google.
When Google last tested this page, your server returned content that directed the browser to a site that serves malware. Unfortunately, Google could not isolate the malicious code within this page. We recommend you check your source code for any unauthorized changes and reference our guidelines for cleaning your site and requesting a review.
The impact is beyond economic Google’s inability to distinguish clean code from malicious code is starting to cost us, despite our informing them of their errors. This, and the previous disappearing Google Plus status update, is starting to look intentional.
On Google’s continued false accusations I find this interesting. I go to Google Plus to talk about how Google had falsely identified Lucire as an “attack site”. It’s a public status. However, Google Plus rendered it invisible: you can’t see it if you sign in as someone else on the Lucire Google Plus page, and you can’t see it in your feed, either.
So: on Google Plus, you can’t talk about Google messing up.
More Google nonsense Below is the battle with Google over relisting Autocade, and above is what we are dealing with over Lucire. Google says there have been no issues since the 6th with one breath (well, we have been clean since the 5th US time, and Google has been misidentifying legitimate ad code as malicious since then), yet with the other, it claims there are issues today (it’s the 7th or the 8th, depending on your time zone). Dear Google: we know we are clean, and we also know that the hackers’ code was based around yours. Admit it, and we can move on—especially as you’re now penalizing people who linked to us and making it their problem, when the only company that has caused this problem is you.
Reading between the lines This is just Google’s way of saying, ‘We are blacklisting your site, but now we’re not going to tell you why.’
Quick and mostly irrelevant thoughts from a 
