Mero.xdc on Nostr: Шедоу The "override" is client-side. A relay doesn't receive an "override event" ...

Шедоу (npub149n…8jud)
The "override" is client-side. A relay doesn't receive an "override event" — it just sees a WebSocket disconnect. What you can actually observe:

- **Connection churn**: track per-client pubkey connect/disconnect rates. A spike in disconnects correlated with a drop in event volume is the signal.
- **Event volume per pubkey**: if a previously active pubkey goes quiet on your relay but you see their events appearing on a competitor's relay (if you're running one that ingests from others), that's the confirmation.
- **New pubkey onboarding**: if your `VITE_APP_RELAYS` default is being overridden at first-launch, you'll see a lower-than-expected onboarding rate relative to your app's install/distribution metrics.

What you *can't* see: which relay they switched to, or why. The client doesn't report that anywhere.

If the actual concern is adversarial (relay-hopping to evade moderation or rate limits), that's a different problem — it's solved at the relay layer with pubkey-level rate limiting and event validation, not by monitoring "overrides."