A number of you have been contacting me over this appearing on Google:
In short, nothing to worry about, it’s all in hand, just waiting for Google to process the site before removing the warning.
In long, we were running WordPress 2.2 which was vulnerable to hacking and someone hacked it. Nothing major, just a bit of link spam. We’ve upgraded to the more secure WordPress 2.5 and cleared away all the spam so all it right with the world.
is it just me with firefox right here right now, or does the new version need javascript enabled in order to post a comment ?
This’ll be where I get amazed that people surf the web with javascript disabled, but I gather it’s not that usual. It’s probably the fancy Ajax comment box not degrading gracefully so I’ll look into it. Eventually.
s’cos there’s too many websites which want to do things like shake your browser, move it about, & resize it to the size *they* want you to have your browser rather than the size *you* want it, innit.
Simon. Dd you last have javascript switched on in about 2001 by any chance?
Simon, Firefox lets you stop scripts from doing that stuff. In preferences where you enable javascript click on “Advanced” (on the Mac version anyway).
Screengrab:
http://skitch.com/peteashton/jaed/picture-2
i just have the noscript extension & add trustworthy sites to the whitelist as & when i come to them…
I saw this Google result for the first time today, and have to say that it’s an irresponsible tactic, particularly if it is highlighting pages that aren’t actively corrupting my machinery. It’s a sure way to drive people away from worthwhile sites. After googling the offending phrase and finding a bunch of stories like yours, I am thinking the line deserves to be replaced with
Scaremongering by Google
Furthermore, I’m not convinced by the Badware site. More hysteria. It looks as though they report sites based on very thin evidence, such as if there’s a link to a site that’s been identified (or misidentified) as corrupt. Bad.
it would also be a bit rich of google to be fixing it on to here because of the ajax for the commenting, given most of their work these days is practically 80% running off it.