v4: a playlist's dump count is of the dumps the viewer may see — it counted every dump in the playlist, so a card said "3 dumps" over a page listing two, and told everyone how many private dumps a playlist held. The lists (/playlists, a profile's playlists and followed ones, the search, a dump's playlists, the add-to-playlist panel) now count by isMemberVisibleTo's rule, in SQL as VISIBLE_DUMP_COUNT (lib/playlist-members.ts): the public dumps, and for the owner their own private ones. GET /api/playlists and /api/users/:key/follow/playlists read the optional sign-in for it. The community page and the digests count the public dumps, their figures being the same for every reader. Live, playlist_created and playlist_updated carry each socket's own count: broadcastChange builds the owner's message and the others' apart. playlist_dumps_updated loses its dumpCount, a client counting the dumps it is sent.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/hooks/playlist/usePlaylistListSync.ts

@@ -85,10 +85,8 @@ export function usePlaylistListSync(
         const idx = prev.findIndex((p) => p.id === ev.playlistId);
         if (idx === -1) return prev;
         const next = [...prev];
-        next[idx] = {
-          ...next[idx],
-          dumpCount: ev.dumpCount ?? ev.dumpIds.length,
-        };
+        // The dumps this user may see, which are those the playlist counts.
+        next[idx] = { ...next[idx], dumpCount: ev.dumpIds.length };
         return next;
       }