Comments

  • Stop The Spam Not Someone’s Privacy

    When I started getting serious about blogging on the WordPress platform with this site, I decided to allow comments on this blog. That is something I never really did much in the past, and I’ve been on this platform since 2014. Even now I’m considering to shut the comments off, however so far I’ve left them on because you never know when someone with an interesting blog or website might have something to say or share that is worth checking out. I already knew that spam comments can get crazy from previous experience, but I decided to let comments happen anyway with requiring approval for all comments before they can appear on this site. Lately my blog has been getting bombed at least once a day with spam comments, and fortunately WordPress has a feature that allows you to enter in names, email addresses, and IP addresses for those spam comments that will block them in the future, and send them directly to Trash, therefore greatly assisting you with automatically curating out unwanted comments.

    For awhile, I have been collecting a list of all that information, and had considered sharing that info in a list for other users to add to their Disallowed Comment Keys in the Discussion settings, but I did some research on it, and was given good reason why we should not be sharing that information, and that marking spam comments as spam is there better choice on the WordPress.com platform, or WordPress in general that utilizes Akismet and Jetpack, which I think these days is probably every WordPress site.

    Provided below are those reasons. The more you know!

    When spam comments pile up on a blog, publishing a list of the names, email addresses, and IP addresses behind them can seem like a helpful way to protect other website owners. However, information collected for comment moderation should not automatically become public content. WordPress.com allows site owners to use these details privately in their discussion settings, but its User Guidelines separately prohibit sharing someone’s personal information without consent. Access to information for managing your website is not the same as permission to distribute it, even when your intention is to help others fight spam. You do not want to become a blogger known as someone who outwardly shares private information. I did not take it into account that comment information, whether it is spam or not, is private information, and should only be used to moderate your own website.

    There is also an important difference between identifying an unwanted comment and identifying the person responsible for it. The information attached to a submission does not necessarily establish who sent it, and an IP address does not always represent a single individual. WordPress.com specifically warns that blocking IP addresses can inadvertently affect other people who share them. Publishing these details as a public “spammer list” can therefore spread an uncertain accusation while encouraging others to block people who had nothing to do with the original submission. Keeping moderation records private helps avoid turning a frustrating spam problem into a privacy problem.

    A shared blocklist can also create problems because WordPress’s filtering tools match information, not verified identities. Disallowed Comment Keys checks entries against several fields, including the comment text, author name, URL, email address, IP address, and browser user-agent string. Broad names, common phrases, or other poorly chosen entries can catch legitimate submissions, and matching comments go directly to Trash rather than waiting for approval. A list that appears effective on one website may be too restrictive for another website’s audience. Sharing advice about careful moderation is therefore more useful than encouraging readers to copy an unverified list of personal details.

    The better response is to mark genuine spam as spam using WordPress.com’s built-in tools. Every WordPress.com site includes Akismet spam protection, and reporting missed spam helps train the filters to recognize unwanted submissions. This contributes to the existing anti-spam system without exposing commenters’ information publicly. Site owners should also distinguish spam from criticism or disagreement, reserving the spam label for submissions that actually warrant it. For uncertain cases, holding comments for moderation provides an opportunity to review them before deciding what to do. Responsible moderation protects both the conversation and the people participating in it, while helping improve spam detection rather than creating a public blacklist.

    So the moral of the story is just mark spam comments as spam, and let others moderate their websites according to their needs.

    Sources:

    1. https://automattic.wordpress.com/privacy-notice/
    2. https://wordpress.com/support/comments/manage-your-sites-comments/
    3. https://wordpress.com/support/ip-addresses/
    4. https://wordpress.com/support/jetpack/
    5. https://wordpress.com/support/protect-from-spam/
    6. https://wordpress.com/support/settings/discussion-settings/
    7. https://wordpress.com/support/user-guidelines/
    (more…)