Remove hardcoded wss://relay.damus.io before its shutdown (end of July 2026)

[dmnyc]

Summary

The operator of wss://relay.damus.io has indicated it will shut down by end of July 2026. Remove all hardcoded references before then so the app doesn't keep trying to connect to a dead relay.

Scope

wss://relay.damus.io is hardcoded in 31 files. In every case it's one entry among several relays in a list/array (never the sole relay), so removal is a safe, mechanical deletion — no replacement relay is needed to preserve redundancy.

Own-line entries (delete the whole line)

• src/components/LongformFoodFeed.svelte:89
• src/components/Recipe/TotalZaps.svelte:22
• src/components/Recipe/TopZappers.svelte:23
• src/lib/engagementCache.ts:11
• src/lib/relaySelector.ts:104
• src/lib/articleOutbox.ts:87 (has trailing comment // Large general relay)
• src/lib/nip17.ts:41
• src/lib/memories.ts:117
• src/lib/queryBatcher.ts:125
• src/lib/connectionManager.ts:69
• src/lib/followOutbox.ts:100
• src/lib/consts.ts:2 (standardRelays — imported by nostr.ts, nostrBackup.ts, spark/index.ts, wallet/nwcBackup.ts, relaySelector.ts, memories.ts, countQuery.ts, settings/+page.svelte, packs/+page.svelte, debug/+page.svelte — widely reused, so this one is worth fixing first)
• src/lib/relayListCache.ts:71
• src/lib/countQuery.ts:48 (trailing comment // 394ms - fast and reliable)
• src/lib/membershipNotificationService.ts:19
• src/lib/recipePackOg.server.ts:13
• src/lib/followRecovery.ts:19
• src/lib/relays/relaySets.ts:23
• src/lib/relays/relaySets.ts:60 (trailing comment // Large general relay)
• src/lib/stores/groupZapReceipts.ts:17
• src/lib/marketplace/products.ts:26
• src/routes/polls/+page.svelte:41
• src/routes/reads/+page.svelte:593
• src/routes/api/counts/batch/+server.ts:29 (trailing comment // 394ms - fast and reliable)
• src/routes/api/counts/[eventId]/+server.ts:22
• src/routes/api/cron/test-notification/+server.ts:111
• src/routes/api/cron/check-expiring-memberships/+server.ts:78

Inline entries (remove just the one array element, keep the line)

• src/components/FoodstrFeedOptimized.svelte:455 — recipes: ['wss://nos.lol', 'wss://relay.damus.io'] → recipes: ['wss://nos.lol']. Also line 452 is a stale benchmark comment naming relay.damus.io (394ms) — worth trimming for accuracy.
• src/components/reads/LongformEditorModal.svelte:391 — relays: ['wss://relay.primal.net', 'wss://nos.lol', 'wss://relay.damus.io'] → drop the last element.
• src/lib/authManager.ts:670 — relays = ['wss://relay.damus.io', 'wss://nos.lol']; → relays = ['wss://nos.lol'];
• src/lib/recipePack.ts:31 — RECIPE_PACK_RELAY_HINTS = ['wss://relay.damus.io', 'wss://relay.primal.net']; → drop the first element.
• src/lib/nourish/nourishPublisher.server.ts:19 — PUBLISH_RELAYS = ['wss://nos.lol', 'wss://relay.damus.io', 'wss://relay.primal.net']; → drop the middle element.

Verification

After removal:

• grep -rn "relay.damus.io" src should return nothing.
• pnpm run check should still pass.
• Spot-check a couple of the affected features (feed loading, zap totals, DM fallback relays, article publish) still work with one fewer relay in their pool.

[dmnyc]

Android (zap_cooking_android) also has this hardcoded

Same relay, same deadline. Filing here since issues are disabled on zapcooking/zap_cooking_android.

wss://relay.damus.io is hardcoded in 8 occurrences across 7 files. Unlike the web app, several of these are in short 2-3 relay arrays where damus is one of only two entries — so a couple of these need a replacement relay chosen, not just a deletion, to avoid losing redundancy.

• app/src/main/kotlin/cooking/zap/app/relay/RelayConfig.kt:27 — DEFAULTS (fresh-install general relay set: nos.lol, relay.damus.io, relay.primal.net) — needs a replacement, this is the app's core default relay set.
• app/src/main/kotlin/cooking/zap/app/relay/RelayConfig.kt:55 — ARTICLES_RELAYS (6 entries) — safe deletion.
• app/src/main/kotlin/cooking/zap/app/relay/RelayConfig.kt:67 — DEFAULT_INDEXER_RELAYS (6 entries) — safe deletion.
• app/src/main/kotlin/cooking/zap/app/relay/RelayConfig.kt:76 — PACK_STANDARD_RELAYS (5 entries) — safe deletion.
• app/src/main/kotlin/cooking/zap/app/relay/RelayProber.kt:37 — BOOTSTRAP (4 entries, used to discover a user's real relay list) — safe deletion.
• app/src/main/kotlin/cooking/zap/app/viewmodel/SplashViewModel.kt:39 — boot-time relay list — check entry count before deciding.
• app/src/main/kotlin/cooking/zap/app/viewmodel/GoogleAuthViewModel.kt:481 — auth-flow relay list — check entry count before deciding.
• app/src/main/kotlin/cooking/zap/app/viewmodel/OnlyFoodFeedViewModel.kt:679 — 3-entry feed query list (nos.lol, relay.damus.io, relay.primal.net) — needs a replacement to keep 3-relay coverage.
• app/src/main/kotlin/cooking/zap/app/viewmodel/FeedSubscriptionManager.kt:83 — subscription relay list (+ a stale comment at line 599 mentioning damus.io).
• app/src/main/kotlin/cooking/zap/app/repo/MemoriesRepository.kt:405 — memories query relays (+ a stale comment at line 194 mentioning damus).
• app/src/main/kotlin/cooking/zap/app/CrashHandler.kt:71 — crash-report relay.

Also CLAUDE.md in that repo documents the fresh-install default relay set (nos.lol, relay.damus.io, relay.primal.net) and will need updating once a replacement is picked.

Open question same as the title implies for the Android side: which relay replaces damus.io in the handful of short lists where it's needed for redundancy? Happy to file/action a separate Android PR once that's decided.