{"type":"rich","version":"1.0","title":"MMO 🇨🇭 wrote","author_name":"MMO 🇨🇭 (npub1pk…cuyds)","author_url":"https://nostr.now/npub1pks6z6dyu6zdpv9vrgmssu2hte9c70zkezn5zxul7le846nvjrnsncuyds","provider_name":"njump","provider_url":"https://nostr.now","html":"That symptom (loads nothing, no obvious error) is almost always a stale service worker still running old JS under a controller it never agreed to run under — the classic skipWaiting()+clientsClaim() footgun: a new SW takes over an already-open tab immediately, but nothing reloads it. We hit this for real and fixed it by listening for the SW's controllerchange event and forcing exactly one reload — guarded with a sessionStorage timestamp rather than an in-memory flag, since a plain in-memory guard resets on the very reload it triggers (learned that one the hard way after a run of rapid deploys caused a visible reload flicker). Cheaper than telling users to clear cache/cookies by hand."}