v4: playlists sort by their last dump, their creation or their size, and /playlists is a grid of covers — every list of playlists came newest first, so one fed every week sank under those made since and left empty. GET /api/playlists and /api/users/:key/playlists take ?sort=updated|new|dumps (PLAYLIST_SORTS, shared/playlist.ts), updated being the default: the last to take a dump first, or its creation while it holds none; a new title, cover or description doesn't bring it back up. A playlist carries that date as lastDumpAt, read with its dumpCount by isMemberVisibleTo's rule (VISIBLE_DUMP_FIGURES, the viewer's id as ?1), so the owner's private dumps date and count their playlists for them alone, in the lists and over the socket: playlist_created, playlist_updated and playlist_dumps_updated carry each socket's own. The /playlists page and a profile's playlists tab show the orders as tabs beside the category menu and keep the one picked in ?sort=, the default being the bare path; a tab takes the current history entry's place, and picking a category keeps the order. Live, usePlaylistListSync takes the list's order: a new playlist goes where it puts it, one that rises moves up to its place, as in the updated order when it takes a dump, and one that falls stays until the list is fetched again, its place being perhaps on a page not loaded. The lists in an order of their own, the followed playlists and the search's, pass none, and take no new playlist as before (noNewEntries goes). comparePlaylists is the order on the client, which a test holds to the API's.

/playlists lays its cards out as tiles, the cover across the top, four to a row and two on a phone, on the wide column: the same PlaylistCard, laid out by its list's class (.playlist-grid), so each theme's card skin carries over. It drops the "public" badge there, every playlist listed being public. On every card, a playlist without a cover shows a tile of its own colour with its initial (ThumbnailPlaceholder) in place of the 📋, and the date is "updated …" of its last dump, or "created …".

A middle, ctrl, cmd or shift click anywhere on a playlist card opens it in a new tab — only its title was a link, the rest navigating by a click handler. useCardLink (hooks/shared) is useDumpCardLink's handlers for any card, which the dump cards now get through it.

A profile tab's query stays with the tab — going from the playlists to the dumps kept the whole query, so a playlist category, and now ?sort=, landed on the dumps' URL. Only the dump lists pass their category to each other; any other change of tab drops the query.

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

src/utils/feed/pagedList.ts

@@ -105,22 +105,39 @@ export function withFirst<T extends { id: string }>(items: T[], item: T): T[] {
 }
 
 /**
- * Returns `items`, newest first as the API pages them, with `item` where its
- * `createdAt` puts it: before the first item no newer than it. An item older
- * than every one loaded is left to a later page, and `items` returned as they
- * are, as they are when `item` is already there. The list sync hooks put a
- * new or newly visible dump or playlist in a list with it.
+ * Returns `items`, in the order of `compare` as the API pages them, with
+ * `item` where that order puts it: before the first item that doesn't come
+ * before it. An item that comes after every one loaded is left to a later
+ * page, and `items` returned as they are, as they are when `item` is already
+ * there. `usePlaylistListSync` puts a new, newly visible or risen playlist in
+ * a list with it, whatever its order.
+ */
+export function withInOrder<T extends { id: string }>(
+  items: T[],
+  item: T,
+  compare: (a: T, b: T) => number,
+): T[] {
+  if (items.some((i) => i.id === item.id)) return items;
+  if (items.length === 0) return [item];
+  const idx = items.findIndex((i) => compare(i, item) >= 0);
+  if (idx === -1) return items;
+  return [...items.slice(0, idx), item, ...items.slice(idx)];
+}
+
+/**
+ * Returns `items`, newest first, with `item` where its `createdAt` puts it,
+ * as {@link withInOrder} does. `useDumpListSync` puts a new or newly visible
+ * dump in a list with it.
  */
 export function withByDate<T extends { id: string; createdAt: Date }>(
   items: T[],
   item: T,
 ): T[] {
-  if (items.some((i) => i.id === item.id)) return items;
-  if (items.length === 0) return [item];
-  const time = item.createdAt.getTime();
-  const idx = items.findIndex((i) => i.createdAt.getTime() <= time);
-  if (idx === -1) return items;
-  return [...items.slice(0, idx), item, ...items.slice(idx)];
+  return withInOrder(
+    items,
+    item,
+    (a, b) => b.createdAt.getTime() - a.createdAt.getTime(),
+  );
 }
 
 /**