Skip to main content

Stopping Comment spam

The big guns- Google, Microsoft and Yahoo have gotten together in the crusade against comment spam with the use of rel=nofollow attribute in the links.

Why it wont score a 10/10?

From the Google blog,
From now on, when Google sees the attribute (rel="nofollow") on hyperlinks, those links won't get any credit when we rank websites in our search results. This isn't a negative vote for the site where the comment was posted; it's just a way to make sure that spammers get no benefit from abusing public areas like blog comments, trackbacks, and referrer lists.
Now, this means that if I add rel=nofollow attribute in the links, then no one can just fool around and increase his website rankings and thereby has no reasons to spam! Right?

But what about those comment spams whose objective is nowhere linked to achieve higher website rankings/pageRanks but is to spread awareness about their 'product', which might be a blog or a brand. All this spam strives for is people visiting these URLs and taking note of their website. In this sort of a situation, I do not see rel=nofollow being of any use.

Comments

Popular posts from this blog

Gmail Chat Disabled

The fact that it happened does not surprise me but that it took so long for our network administrators to figure it out does. And if you are wondering how do you disable Gmail's chat features on your network, you only need locking DNS lookups to chatenabled.mail.google.com , by returning 127.0.0.1 .

Advertising Billboards as Rain Covers

Advertising billboards are put to use as Pakistani refugees, left homeless after the October 8 earthquake, set up their tents in Muzaffarabad, Pakistan. [via SFGate ] Technorati Tags: Pakistan Earthquake

Community effort to create a single persistence model for the Java community

A community effort led by Sun Microsystems is aiming to create a single 'Plain Old Java Object' persistence model to provide a single object/relational mapping facility for Java app developers in J2SE and J2EE. Paul Krill writes In a letter to the “Java Technology Community” on Friday, specification leads on Java Specification Request (JSR) 220, which is the proposal for Enterprise JavaBeans 3.0, and JSR-243, for Java Data Objects, state that the two technologies feature divergent persistence models. “This divergence has caused confusion and debates among Java developers, and is not in the best of interest of the Java community,” said JSR-220 leader Linda DeMichiel who also is a Sun employee, and Craig Russell, a staff engineer at Sun who leads JSR-243. “In response to these requests [for an end to the unwanted divide], Sun Microsystems is leading a community effort to create a single POJO (Plain Old Java Object) persistence model for the Java community,” the letter said.