No. SleekView Feedback reads directly from wp_comments joined with the Akismet meta keys in wp_commentmeta. You point it at the source, pick the columns for votes, status, category, and reviewer, and the board renders without any sync step or duplicated data.

Yes. SleekView ships with anonymous voting backed by cookies and a logged in mode that respects WordPress capabilities. Most publishers expose a slim public page that lets logged in readers flag any decision they think was wrong, with full triage tools restricted to editors.

Each visitor gets a cookie scoped vote token per item, and logged in users are tracked by user ID. The plugin also exposes a rate limit so a single IP cannot spam the board, which keeps the false positive queue honest without forcing a signup wall in front of readers.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to a specific Akismet result, a specific post type, or a specific date range. Different pages can show different boards, which is how teams build per category review queues.

False positive is just a category value on the row, stored in comment meta. The value shows up next to the comment in the WordPress admin moderation screen, so the admin who owns Akismet settings sees every flag without leaving WordPress.

Upvotes write back to comment meta, and the plugin exposes a resubmit hook you can wire to the Akismet API to submit high score false positives for retraining. Several publishers use this to feed Akismet a steady signal of true false positives from real readers.

Both. SleekView ships as a Gutenberg block, an Elementor widget, a Bricks element, and a classic shortcode. Theme developers can also call the render function from PHP and pass a configuration array, so you can mount the board on any custom moderation dashboard.

The view paginates server side and only loads the rows it needs to render the current page. You can index the comment date, score, and status columns, and SleekView will use them. Publishers with millions of historic comments run the board without measurable load on the comments table.