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>

api/routes/users.ts

@@ -245,10 +245,16 @@ router.get("/:key/follow/users", (ctx) => {
   ctx.response.body = responseBody;
 });
 
-router.get("/:key/follow/playlists", (ctx) => {
+router.get("/:key/follow/playlists", async (ctx) => {
   const user = resolveUserKey(ctx.params.key);
+  const requestingUserId = await parseOptionalAuth(ctx);
   const { page, limit } = parsePagination(ctx.request.url.searchParams);
-  const { items, hasMore } = getFollowedPlaylistsByUser(user.id, page, limit);
+  const { items, hasMore } = getFollowedPlaylistsByUser(
+    user.id,
+    requestingUserId,
+    page,
+    limit,
+  );
   const responseBody: APIResponse<PaginatedData<Playlist>> = {
     success: true,
     data: { items, hasMore },