Yes. SleekView reads the underlying wp_bp_follow table directly, which both plugins populate using the same column shape. Sites that have migrated between BuddyPress Followers and BuddyBoss keep the same follow graph, so the SleekView config keeps working across the migration without any extra remapping required.

Yes. The data source picker lets you define a derived column that multiplies a reaction count by the author's follower count, or you can use a custom meta that an integration writes to whenever a follower reacts. Both options produce a follower-weighted board without any database migration.

It refreshes on every render and caches the sorted set briefly for performance. New follow events are reflected on the next cache expiry, which is configurable, so a Top voices page can refresh every few minutes while a roadmap board can refresh hourly without pressuring the database.

It writes to whichever meta or favorites table you mapped in the config. Most sites point at the standard BuddyPress favorites table so reactions stay consistent across the stream, while sites that need a dedicated upvote column add a small custom meta that lives alongside the activity row.

Unfollow events drop the row from wp_bp_follow, and the next board refresh recomputes the follower count for the affected author. There is no cache of stale relationships, so a member who unfollows quickly stops contributing weight to that author's posts on the board.

Yes. The data source picker accepts a meta query or a derived filter, so a Threshold board scoped to authors with at least one hundred followers takes a few seconds to configure. New members appear on the board only after they hit the threshold, which gives early-stage accounts a clear growth target.

No. The follower count for the current page of activity posts is computed from indexed rows and the result is cached, so a board on a site with millions of follow relationships renders in the same time as a small community board because the heavy join only runs once per cache window.

The board falls back to the configured upvote column without the follower-weighting join. If the upvote column is a follower-weighted derived column it returns zero for every row, so you would typically reconfigure it to a meta or favorites column before deactivating the Followers plugin to avoid an empty board.