Earlier quoted context omitted.
The set of strings is isomorphic to a Cartesian Product of sets of the same cardinalities as the set of options (for example, if the template was "{I,We} like {HTML, CSS, Javascript}", you can make a set {0,1}x{0,1,2}, where each element in the product set maps to one string and vice versa. For example (0,0) might represent I like HTML, and (1,2) might represent We like Javascript). Because there is a one to one map…
Multiply the count in each set, gotcha. But did he just count it for each set? It seems like that would be time consuming. Is there some shortcut? or did he just write a quick program to do it?
Comment spam random text template
71–76 of 76 posts
Re: Comment spam random text template
#72I have a friend who works for a large marketing company where they write website content for companies that looks almost identical to this. The company hires hundreds of young writers at a time and pays them minimum wage to come up with a few of these every day. They pass their paragraphs around to other writers who reword it again so it will show up as a unique site for search engines. I call it the spam factory.
What's the company?
Re: Comment spam random text template
#73Re: Comment spam random text template
#74Re: Comment spam random text template
#75Earlier quoted context omitted.
I have the website field turned off -- it's not visible if you are a real user using the form, and "website" doesn't show up next to comments. But I still get a lot of spam containing the website field; it seems like the bot is just automatically submitting POST requests with website included. This should be trivial to detect -- is there a plugin that just immediately deletes all of these out of hand before passing t…
There's a way of setting the 'hidden' property on an input field and checking if the field is blank. If it's a bot sending POST requests, there's a high chance a "Website:" field would be filled out. Innocent users will not be able to fill out the field, in the case of a legitimate comment.
Also, many spammers hit the wp-comments-post.php file directly. Since they hit it directly there is no referrer passed like there would be if a POST was sent to it from a page on your site. This page: http://goo.gl/n5VHm on WordPress.com has information on code that can be added to your .htaccess file that will crush bots that POST to wp-comments-post.php with no referrer present.