You might not need a service worker
Fudgel
18 points
2 comments
June 29, 2026
Related Discussions
Found 5 related stories in 639.6ms across 14,015 title embeddings via pgvector HNSW
- JavaScript Is Enough arbayi · 20 pts · March 22, 2026 · 49% similar
- Do you even need a database? upmostly · 231 pts · April 15, 2026 · 47% similar
- Show HN: Flashbang – DuckDuckGo bangs resolved locally with a Service Worker t3ntxcles · 15 pts · July 14, 2026 · 46% similar
- Show HN: Kyushu – A self-hostable WASM sandbox for JavaScript workers le_chuck · 74 pts · June 07, 2026 · 45% similar
- Maybe Don't Rely on Google's "Modern Web Guidance" klueinc · 11 pts · June 03, 2026 · 45% similar
Discussion Highlights (2 comments)
jakelazaroff
While working on a small atproto OAuth client I discovered a neat service worker pattern that I don't think I've ever seen someone write about. The page makes normal fetch requests, and the service worker adds the authorization header and handles token refreshes/dpop retries/etc under the hood. https://tangled.org/jakelazaroff.com/atsw
cheema33
> I’d argue that this is more of a question of ‘do I need offline support?’ For Slack, sure, but for many apps, probably not. I like offline support. I enjoy it when an app I use supports it. And I want to add support for it in my own app. But, it is a hard problem. And to the best of my knowledge there is no framework or library that that solves the hard problems for you.