Yes. Both versions store enriched media inside the standard BuddyPress activity table and meta, which SleekView reads directly. Sites running either fork get the same configuration options for media-type categories, favorite-count upvotes, and status pills without any plugin-specific tweaks to the data source.

Yes. SleekView delegates the media rendering to whatever theme and Activity Plus add-on is active, so a photo card on the board looks identical to a photo card in the activity stream. Only the surrounding wrapper, the upvote button, and the status and category pills come from SleekView.

Yes. SleekView respects the same meta flags Activity Plus uses to mark sensitive media, so a flagged post renders with the click-to-show wrapper intact. The status pill can also be wired to a Sensitive value so moderators see which posts have been gated without needing to expand each one individually.

Yes, if you mapped the upvote column to the favorites table. Each click writes a new favorite row exactly like the heart button on the activity stream would, so the same engagement signal feeds notifications, the activity stream, and any BuddyBoss App bridge or third-party reporting plugin.

Edited posts stay on the board with their updated content, and the favorite count and reactions on the original post carry over because the underlying row keeps the same ID. Moderation timelines remain accurate because the activity meta is not rewritten by SleekView during the edit.

No. SleekView paginates the underlying query, caches the sorted set, and uses indexed columns for the favorite-count join. A board with fifty thousand Activity Plus posts renders in the same time as a board with five hundred because the database does the work once and the cache covers the rest.

Yes. Each SleekView block accepts its own data source filter, sort column, and status mapping. A Photos board, a Links board, and an Embeds board can each live on its own page with its own pills, sharing the same underlying BuddyPress favorites table for engagement counts.

The board keeps rendering against the underlying BuddyPress activity table, but rich-media rendering falls back to plain activity content because Activity Plus is the layer that produces the photo and link cards. Reactivating Activity Plus restores the rich rendering without any SleekView reconfiguration.