shakespeare.diy
409d443dbd
The NPool's 500ms eoseTimeout causes event-by-ID queries to resolve before slower relays respond. Previously, useEvent returned null on the first miss and the page immediately showed a 404. Now: - useEvent/useAddrEvent throw on miss so TanStack Query retries (3 retries with exponential backoff: 2s, 4s, 8s) - PostDetailPage shows the skeleton while retrying (checks isFetching) - Only shows 404 after all retries are exhausted - Feed cache seeding from previous commit still provides instant navigation for events already seen in the feed Co-authored-by: shakespeare.diy <assistant@shakespeare.diy>