93bf6171515448cb01bb9e441f04e35e8d0a4a1c
A history row is only as fresh as the last list load, and the list was only read on mount — so a search you had just started sat at 0 responses looking stalled until you navigated away and back. slskd's own web UI goes straight to the search when you submit, and that view already polls while the search runs, so follow it. Which search is open now lives in ?search=<id> rather than local state: rows are real links, Back returns to the history, and a reload keeps your place. The list also keeps re-reading while any search is still running. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Description
No description provided
42 MiB
Languages
TypeScript
90.9%
Shell
4.7%
JavaScript
4.1%
CSS
0.2%
HTML
0.1%