Replace homebrew list virtualization with react-window

[Copilot]

Replaces the custom ProgressiveRender component with the react-window library for proper list virtualization across all list views.

Changes

New VirtualizedList component (src/common-components/virtualized-list.jsx)

• Wraps react-window's List with viewport height calculation, ad insertion (every 35 items), and infinite scroll detection
• Configurable item height and onReachEnd callback for pagination

Updated list views to use VirtualizedList:

• Block panel lists (blocked users)
• User lists
• Blocking lists
• Post history

Removed:

• ProgressiveRender component
• Progressive rendering state management in HistoryScrollableList (now handled by virtualization)

Example

Before (homebrew progressive rendering):

<ProgressiveRender
  items={blocklist}
  renderItem={(item) => <ListViewEntry {...item} />}
/>

After (react-window virtualization):

<VirtualizedList
  items={blocklist}
  renderItem={(item) => <ListViewEntry {...item} />}
  itemHeight={60}
/>

The virtualized list only renders visible items in the DOM, significantly reducing memory usage and improving scroll performance for large lists while preserving ad placement and pagination behavior.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• staging.api.clearsky.services
  • Triggering command: node /home/REDACTED/work/ClearskyUI/ClearskyUI/node_modules/.bin/vite --open (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Use true list virtualization for all list views</issue_title>
<issue_description>currently the block-panel-generic has a homebrew form of list virtualization but we should be using that everywhere. and probably something more robust, such as the react-window package.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Use true list virtualization for all list views #153

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
clearsky-ui	Ready	Preview	Comment	Nov 14, 2025 5:19pm

[thieflord06]

@copilot Where in the code is staging.api.clearsky.services referenced?

[Copilot]

@copilot Where in the code is staging.api.clearsky.services referenced?

The reference to staging.api.clearsky.app (note: .app, not .services) is in src/api/core.js line 24. This was not added by my changes - it exists in the base commit (2cf880d).

The staging URL is used when:

1. The ?api=staging query parameter is present, OR
2. The site is accessed from a hostname other than clearsky.app (defaults to staging)

This is defined in the getApiBase() function on lines 32-41 of src/api/core.js.

[thieflord06]

@copilot staging.api.clearsky.services isn't in the current codebase and only one domain is being used, can you merge the latest commits and verify that this addresses the issue?

[Copilot]

@copilot staging.api.clearsky.services isn't in the current codebase and only one domain is being used, can you merge the latest commits and verify that this addresses the issue?

Verified: The codebase is already using the unified clearsky.app domain.

Key findings:

• ✅ No references to staging.api.clearsky.services exist anywhere in the codebase
• ✅ All references use staging.api.clearsky.app (unified domain)
• ✅ My PR changes don't modify any domain-related code
• ✅ Build completes successfully

The domain unification was already done in the base commit (2cf880d "Update to use same domain") before my virtualization changes. The current code correctly uses only clearsky.app throughout.