The Discover page currently fetches up to 100 peers from the backend and renders all of them in a single grid dump. There is no pagination, no Load More button, and no way for the user to navigate results in batches. On slower connections or large datasets this means a long wait followed by a wall of 100 cards. This PR adds client-side pagination with a PAGE_SIZE of 12 cards per page. A pagedUsers slice is derived with useMemo from the full filteredUsers array, and a "Load More (N remaining)" button is rendered below the grid when more results exist. The page counter resets to 1 whenever the search or filter changes so users always start from the top of new results. This also partially addresses issue #953 by reducing the visible payload on first render without requiring any backend changes.
PLEASE ASSIGN THE ISSUE TO ME UNDER GSSOC'26
The Discover page currently fetches up to 100 peers from the backend and renders all of them in a single grid dump. There is no pagination, no Load More button, and no way for the user to navigate results in batches. On slower connections or large datasets this means a long wait followed by a wall of 100 cards. This PR adds client-side pagination with a PAGE_SIZE of 12 cards per page. A pagedUsers slice is derived with useMemo from the full filteredUsers array, and a "Load More (N remaining)" button is rendered below the grid when more results exist. The page counter resets to 1 whenever the search or filter changes so users always start from the top of new results. This also partially addresses issue #953 by reducing the visible payload on first render without requiring any backend changes.
PLEASE ASSIGN THE ISSUE TO ME UNDER GSSOC'26