Yes. SleekView reads the wp_wpdiscuz_emoticons table directly, and that schema is identical across the free and Pro builds. Every reaction key, positive or negative, is exposed the same way, which means the board ranking and writes work regardless of which tier of the plugin you have installed.

Yes. SleekView lets you assign a weight per emoticon key, so a heart can count for two while a thumbs up counts for one, and a negative key can subtract from the total. The weighted sum becomes the rank column and the same weights apply when readers filter by total reactions on the board.

The in-thread emoticon strip keeps working exactly as wpDiscuz Emoticons intended. SleekView only adds a ranked board on top of the same data, so reactions from inside a thread and reactions from a board card both write to the same table and update both surfaces in real time.

Both count by default, with anonymous reactors hashed by IP and cookie identifier exactly the way wpDiscuz Emoticons already does for in-thread reactions. You can also restrict the board to logged in users only with a toggle, which is a common choice for membership and private community sites.

Live mode pushes only deltas over a websocket channel, not full payloads, so even a viral reaction storm stays well within typical hosting capacity. You can also fall back to a thirty second polling interval, which still keeps the board feeling current without holding a long-lived connection open.

Yes. The SleekView toolbar includes a CSV export that honors any filter currently applied. The export carries titles, total positive reactions, total negative reactions, authors, statuses, and category tags, so it drops neatly into a spreadsheet or any third party analytics pipeline you already use.

Yes. SleekView calls into the wpDiscuz Emoticons write path for every Upvote click, which means rate limits, duplicate prevention, and any anti-spam filters you have configured apply to board reactions the same way they apply to reactions placed directly on a comment in the thread view.

Yes. SleekView never owns wpDiscuz Emoticons data, it only reads from and writes to the same table the plugin already manages. Removing SleekView leaves every reaction row and every comment in place, so the default emoticon strip keeps working with no rebuild or migration step required.