Raihanul Islam

<p>This is the long description.  No limit, and you can use Markdown (as well as in the following sections).</p>
<p>For backwards compatibility, if this section is missing, the full length of the short description will be used, and<br />
Markdown parsed.</p>
<p>A few notes about the sections above:</p>
<ul>
<li>“Contributors” is a comma separated list of wordpress.org usernames</li>
<li>“Tags” is a comma separated list of tags that apply to the plugin</li>
<li>“Requires at least” is the lowest version that the plugin will work on</li>
<li>“Tested up to” is the highest version that you’ve <em>successfully used to test the plugin</em>. Note that it might work on<br />
higher versions… this is just the highest one you’ve verified.</li>
<li>
<p>Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use <code>/trunk/</code> for<br />
stable.</p>
<p>Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so<br />
if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that’ll be used<br />
for displaying information about the plugin.  In this situation, the only thing considered from the trunk <code>readme.txt</code><br />
is the stable tag pointer.  Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in<br />
your in-development version, without having that information incorrectly disclosed about the current stable version<br />
that lacks those changes — as long as the trunk’s <code>readme.txt</code> points to the correct stable tag.</p>
<p>If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where<br />
you put the stable version, in order to eliminate any doubt.</p>
</li>
</ul>
<h3>Arbitrary section</h3>
<p>You may provide arbitrary sections, in the same format as the ones above.  This may be of use for extremely complicated<br />
plugins where more information needs to be conveyed that doesn’t fit into the categories of “description” or<br />
“installation.”  Arbitrary sections will be shown below the built-in sections outlined above.</p>
<h3>A brief Markdown Example</h3>
<p>Ordered list:</p>
<ol>
<li>Some feature</li>
<li>Another feature</li>
<li>Something else about the plugin</li>
</ol>
<p>Unordered list:</p>
<ul>
<li>something</li>
<li>something else</li>
<li>third thing</li>
</ul>
<p>Here’s a link to <a href="https://wordpress.org/" title="Your favorite software" rel="ugc">WordPress</a> and one to <a href="http://daringfireball.net/projects/markdown/syntax" title="Markdown is what the parser uses to process much of the readme file" rel="nofollow ugc">Markdown’s Syntax Documentation</a>.<br />
Titles are optional, naturally.</p>
<p>Markdown uses email style notation for blockquotes and I’ve been told:</p>
<blockquote>
<p>Asterisks for <em>emphasis</em>. Double it up  for <strong>strong</strong>.</p>
</blockquote>
<pre><code><?php code(); // goes in backticks ?>
</code></pre>


Awesome Post Views Counter

Here is a short description of the plugin.  This should be no more than 150 characters.  No markup here.

Gulshan Kumar

<p>The fastest and GDPR compliant Anti-Spam plugin to prevent bot spam in the <strong>Default Commenting System</strong> of WordPress.</p>
<h3>Important</h3>
<ul>
<li>Please clear page cache after plugin activation.</li>
<li>Only for default commenting system. Not for AMP.</li>
</ul>
<h4>Features</h4>
<ul>
<li>100% GDPR Compliant.</li>
<li>Captcha-Free solution.</li>
<li>Requires no settings.</li>
<li>Automatic. No need of false-positive comment moderation.</li>
<li>Compatible with all page caching and performance optimization plugins.</li>
<li>Fastest ever. A tiny inline JavaScript in just ~200 bytes does all magic.</li>
</ul>
<h4>How does it work?</h4>
<p>To prevent spam comments plugin blocks the default action path (wp-comments-post.php) for bots and make it accessible over unique hash query string when a visitor scroll to leave a comment. This way it prevents automated spam comment done by bots.</p>
<p><strong>Video Demonstration</strong></p>
<p><span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/uwIfk08GSwk?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span><br />
Watch on <a href="https://www.youtube.com/watch?v=uwIfk08GSwk" rel="nofollow ugc">YouTube</a></p>
<h3>Let’s support each other 🙏</h3>
<ul>
<li>Please Upvote Forget Spam Comment plugin at <a href="https://www.producthunt.com/products/forget-spam-comment#forget-spam-comment" rel="nofollow ugc">Product Hunt</a></li>
<li>You can <a href="https://www.gulshankumar.net/contact/" rel="nofollow ugc">contact me</a> to report any issues. I’d be happy to assist.</li>
</ul>


Forget Spam Comment


This is the best ultra-simple (and free) way to stop comment spam, thanks to the method it uses. Alternative effective solutions are more complicated and involve webserver configuration or WAF and CAPTCHA services. Other plugins simply fail to address the root cause of comment spam. This is the one to use.


Simply the Best

The ultimate solution to stop spam comments in the default commenting system of WordPress

Awesome Post Views Counter vs Forget Spam Comment