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>

shared/ws.ts

@@ -295,7 +295,8 @@ export interface PlaylistCreatedMessage {
 
 /**
  * Sent by the server when a playlist changes, to every socket if it is public,
- * else to its owner's, as when it has just gone private.
+ * else to its owner's, as when it has just gone private. Its `dumpCount` is
+ * the socket's user's, as in `playlist_created`.
  */
 export interface PlaylistUpdatedMessage {
   type: "playlist_updated";
@@ -325,8 +326,6 @@ export interface PlaylistDumpsUpdatedMessage {
    * private dump is left out.
    */
   dumpIds: string[];
-  /** Counts every dump, hidden ones included, as `Playlist.dumpCount` does. */
-  dumpCount: number;
 }
 
 /**