nrobi144 552540e77d fix(desktopApp): move sleep/resume detection out of Quartz ...

Per Vitor's review of #3221: wake-detection is platform-specific UX, not
NostrClient's job. Quartz already exposes `reconnect(onlyIfChanged = false,
ignoreRetryDelays = true)` which does the full disconnect + connect — the
app layer just needs to call it when it detects a wake.

- Revert the keep-alive heuristic in NostrClient.kt; the loop is back to the
  conservative `reconnectIfNeedsTo` path it had before.
- Add `runSleepResumeMonitor` (desktopApp/network/SleepResumeMonitor.kt): a
  60s tick that watches for wall-clock overshoot and calls the supplied
  `onWake` lambda. No native deps.
- Wire it in `Main.kt` next to the metrics LaunchedEffect: on >5x overshoot
  call `relayManager.client.reconnect(onlyIfChanged = false,
  ignoreRetryDelays = true)`.

Real OS sleep events (NSWorkspace on macOS, D-Bus PrepareForSleep on Linux,
WM_POWERBROADCAST on Windows) can be layered in later as platform improvements
without touching Quartz again.

2026-06-16 09:59:31 +03:00

..

jvmMain

fix(desktopApp): move sleep/resume detection out of Quartz

2026-06-16 09:59:31 +03:00

jvmTest/kotlin/com/vitorpamplona/amethyst/desktop

feat(model): count NIP-18 quote-reposts in the repost counter

2026-06-09 20:15:19 +00:00