What are spam comments?
Spam in blogs (also called simply blog spam or comment spam) is a form of spamdexing. It is done by automatically posting random comments or promoting commercial services to blogs, wikis, guestbooks, or other publicly accessible online discussion boards. Any web application that accepts and displays hyperlinks submitted by visitors may be a target.
Adding links that point to the spammer’s web site artificially increases the site’s search engine ranking. An increased ranking often results in the spammer’s commercial site being listed ahead of other sites for certain searches, increasing the number of potential visitors and paying customers.
Examples of en.grand-piano.org’s comment spam. Click image to see more examples of the unrelated posts they’ve been commenting on.
If you’re in the market for a new Grand Piano, please take their questionable tactics into consideration before making your final decision. If are willing to use such lowly methods to gain customers, can you really trust the way they handle other aspects of business?
Who engages in this practice, presumable to increase search engine prominence and thus sales?
I use JS-Kit to handle comments on my blog, and so have disabled WordPress’ native commenting system. Yet everyday I receive emails informing me that “PianoGuy”, “GoPiano”, “PianoDraft”, “PianoTrade”, “PianoFan”, “LePiano” … found posts as unrelated to Pianos as: “Write Your Own Listener Interface (you know you want to)” or “Auto-Notification of Broken Links, Fantastic Pre-Written Anti-Spam .htaccess File!” (irony?) interesting and helpful.
Mr. PianoMan, this behaviour is not acceptable. We would like you to please leave our blogs never return. Or if you do insist on reading our posts, at least wait until we write something actually related to Pianos before leaving a
Update: the spambot has attempted to comment on this post!
I wanted the little app I’m making to display a green tick or a red cross depending on whether the user had entered valid credentials. Simple? Yeah. Everything went really well, I extended a JPanel to handle the tick/cross display area (tickCross), got the POST code going, strung together the rest of the GUI elements.
The problem was that tickCross.repaint() wasn’t reliably repainting. about 30% of the time the image wouldn’t be painted. The method was being called, but nothing was happening. I tried Google, re-read the related Sun Java docs and was reminded that: “repaint() does not actually paint. It calls the peer repaint which enqueues a request in some platform-dependent way inside the native GUI for a repaint.” – MindProd. Great. My OS was deciding when I was allowed to draw.