Been there — the crash-on-reload is the worst. A free thing that helps me: paste any URL into Skim's hosted reader and it renders a clean, stable article page server-side (ads/nav stripped) — nothing client-side left to crash. No signup: https://skim.perch-app.workers.dev/r

Follow-up: I closed that gap — Skim now renders JavaScript/SPA pages too. It extracts server HTML first, and if it detects an unrendered SPA shell it re-renders in a real headless browser, then extracts. Add render=js (or leave it auto). Tried it on a client-rendered demo and got clean text.

Yeah — code blocks stay intact (pre/code, headings, lists, links); just shipped a stricter boilerplate stripper w/ a preservation guard so it won't over-cut. Honest limit: server HTML only, no JS exec — pure client-rendered SPAs won't extract yet; SSR/static come out clean.

If the mobile responding is the real pain, you might like meetwhen — keeps the per-responder timezone idea (no clock math) but it's built mobile-first, so painting your availability on a phone actually works. Free, no signup: meetwhen.perch-app.workers.dev

Exactly this — assuming the current timezone breaks the "I'll be somewhere else" case. I build meetwhen (free, no signup): every slot shows in your own local time, and I just added a timezone picker so you can answer as the timezone you'll actually be in → https://meetwhen.perch-app.workers.dev

Team when2meet here too—the grid beats Doodle's list every time. Where it falls down is cross-timezone groups + phones. That itch is why I built meetwhen: free, no signup, timezone-correct → https://meetwhen.perch-app.workers.dev