Linux 软件免费装
Banner图

Quarivo Comment Shield

开发者 taka235345
更新时间 2026年8月3日 09:52
PHP版本: 7.4 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

comments spam security antispam moderation

下载

2.2.9 2.3.0 2.3.1 2.3.2 2.2.2 2.2.4 2.2.6 2.2.7

详情介绍:

Activate it once. Quarivo Comment Shield quietly handles obvious spam. Quarivo Comment Shield is a local, low-overhead comment spam filter built for site owners who want less notification noise without losing potentially important messages. It combines several independent signals with three selectable protection modes. Balanced mode treats every language equally, while Japanese-site enhanced and Strict Japanese modes can apply a reversible site-language policy chosen by the administrator. Three protection modes A review inbox designed for real work Quiet protection with safe defaults Conservative local learning When a moderator restores or approves a false positive, or marks a comment as spam, the result is recorded locally. This works in both the Quarivo review inbox and the ordinary WordPress Comments screen. Repeated false positives can slightly reduce selected soft-signal weights. An exact author Website repeatedly confirmed as spam can add only a small supporting score when that same Website is also linked in a future comment. The stored Website key is hashed, expires after 180 days, and is capped at 500 entries. Campaign similarity memory also creates versioned, non-readable signatures from human-reviewed comments. It normalizes URLs, rotating numbers, generated identifiers, and small wording changes so variants of one campaign can supply supporting evidence. A similar restored legitimate comment vetoes that learned spam score. Similarity never blocks a comment by itself, trusted commenters remain exempt, and automatic quarantine is never used as training data. Earlier retained moderator verdicts are imported in bounded, resumable batches after the update. If learning storage becomes unavailable, the import cursor is retained, a bounded retry is scheduled, and campaign matching fails open until storage is verified again. Campaign signatures stay in the site's database, expire after two years, and are capped at 5,000 entries. They survive normal updates and are retained by the default plugin-removal setting. If a moderator later corrects a verdict, the earlier versioned signature is replaced or removed rather than counted twice. Strong security signals are never weakened automatically. “Publish and learn” can also allow the exact submitted email address. The plugin does not automatically trust a shared IP address or an entire email domain. Privacy and retention Quarantined comments and hashed campaign-learning signatures remain on the site's own database and are not sent to an external service. The plugin integrates with WordPress personal-data export and erasure tools. Unreviewed quarantined comments are never removed automatically. Equivalent repeated submissions are grouped into one record, and a finite admission ceiling prevents unlimited growth. When capacity is unavailable, comments fall back to normal WordPress moderation. Confirmed-spam and restored records are removed after the administrator's selected retention period (30 to 365 days). Action history is retained for up to one year. If WordPress deletes the plugin, Quarivo data is retained by default so possible false positives can be recovered after reinstalling. Administrators can first download a private JSON export or explicitly choose permanent removal under Settings > Data and removal. Permanent removal deletes only Quarivo tables, settings, learning data, and Quarivo comment metadata; ordinary WordPress comments, posts, users, and media are not deleted.

安装:

  1. Upload the quarivo-comment-shield folder to /wp-content/plugins/, or install it from the WordPress plugin directory.
  2. Activate Quarivo Comment Shield through the Plugins screen.
  3. Use the activation guide, or open Comments > Quarantined Comments, to review candidates. Basic protection needs no setup.
  4. If another plugin also blocks or discards comments, test carefully and deactivate the overlapping filter to avoid double decisions.

屏幕截图:

  • Full comment review modal with reasons, details, history, and restore actions.
  • Local learning dashboard showing allowed email addresses and conservative score calibration.
  • Privacy-aware retention, private data export, and safe plugin-removal controls.

升级注意事项:

2.3.2 Fixes a review-count mismatch and makes every unreviewed WordPress-held candidate reachable from the priority inbox. 2.3.1 Adds durable, reversible campaign similarity learning. Earlier retained moderator verdicts are imported automatically in bounded batches. 2.3.0 Adds three selectable protection modes. Review the mode after updating if legitimate readers may comment in languages other than Japanese. 2.2.12 Closes a shortened-link reward-lure bypass while preserving ordinary redirected references and quoted scam warnings. 2.2.11 Closes a compact bare-link bypass with a conservative multilingual structural rule while preserving plausible feedback and substantive link sharing. 2.2.10 Closes a compact gambling-link bypass and adds a conservative brand-independent layer for future machine-link promotion campaigns. 2.2.9 Protects possible-important comments from bulk mistakes, adds reversible spam confirmation, and keeps review counts synchronized with their filtered list. 2.2.8 Adds conservative structural detection for automated comments that disguise promotional links as neutral article recommendations. 2.2.7 Keeps reviewable Quarivo data recoverable by default during plugin deletion, adds an explicit permanent-removal choice and private JSON export, and makes confirmed-spam records immediately visible.

常见问题:

Does it quarantine every non-Japanese comment?

Only when Strict Japanese is selected and the commenter is not already trusted. Balanced never treats a language as suspicious, and Japanese-site enhanced also requires an external link or submitted Website. In every mode the comment is quarantined for review rather than permanently deleted, and a restored or previously approved commenter can be trusted safely.

Can I restore a legitimate comment?

Yes. Open the comment in the review inbox and restore it either as pending or published. You can also publish it and teach the plugin to trust that exact email address.

Does learning send comments to an AI or external API?

No. Feedback and score adjustments stay in the local WordPress database. No external service is used.

Can learning make protection unsafe?

Learning uses only human moderator feedback and is tightly capped. False-positive history can slightly reduce selected soft signals. A single matching campaign confirmation remains a small supporting signal; repeated independent confirmations can add a larger but bounded score. Similarity never blocks a comment by itself, and a matching restored comment vetoes the campaign score. Honeypot hits and other strong signals are not weakened automatically.

Will my learning disappear after an update or reinstall?

No during a normal update. Campaign signatures are stored in a dedicated versioned table and earlier retained verdicts are imported in resumable batches. WordPress plugin deletion retains the table by default, so reinstalling reconnects it. Learning is removed only by the explicit Reset learning history action, by choosing permanent Quarivo data removal before plugin deletion, or by the documented two-year/5,000-signature safety limits.

What happens to old quarantine records?

Only reviewed records marked as confirmed spam or restored are removed after the selected retention period. Equivalent repeats are grouped. Unreviewed records remain until a moderator handles them, subject to a finite capacity; overflow falls back to WordPress moderation rather than being discarded.

Can I process thousands of quarantined comments at once?

Yes. Choose a filter, select “all matching results,” and apply the action. The browser requests a small server-side batch at a time and shows progress. The job has a fixed upper boundary so newly arriving comments are not unexpectedly included, retries brief connection failures, and can resume when the same moderator returns. Keep the review screen open while it is actively running. As an extra false-positive safeguard, unopened comments with an assessment score of 9 or lower are never included in bulk spam confirmation. Open those possible-important comments first and decide individually. High-confidence queues remain eligible for safe staged processing.

What data is stored?

For quarantined comments, the plugin stores the submitted name, email address, URL, comment, IP address, browser information, submission time, target post, and local assessment details. This data remains on the site and is included in WordPress privacy export and erasure requests.

What happens on uninstall?

By default, WordPress plugin deletion retains quarantine records, action history, settings, local learning, and Quarivo comment metadata. Reinstalling Quarivo reconnects that data and shows a recovery notice. Temporary jobs, locks, and scheduled tasks are removed. Before deletion, open Comments > Quarantined Comments > Settings > Data and removal. You can download a private JSON export for safekeeping or explicitly enable permanent removal. The JSON export is not imported automatically. Permanent removal requires a confirmed saved choice and deletes only Quarivo data; ordinary WordPress comments, posts, users, and media are never removed. While the plugin is absent, its review screen and WordPress privacy exporter/eraser are unavailable.

Where did a comment go after I confirmed it as spam?

It was not immediately deleted. Open the Confirmed spam count at the top of the review inbox, or choose Confirmed spam from the status filter. The record remains reviewable until you explicitly delete it or the reviewed-record retention period ends. If the confirmation was a mistake, open the record and choose Undo spam confirmation. It returns to quarantine without being published, and the earlier local-learning vote is reversed.

更新日志:

2.3.2 2.3.1 2.3.0 2.2.12 2.2.11 2.2.10 2.2.9 2.2.8 2.2.7 2.2.6 2.2.4 2.2.3