Offline with Service Workers was a session at IndieWebCamp Düsseldorf 2017.
Notes archived from: https://etherpad.indieweb.org/iwcdus17_serviceworker
IndieWebCamp Dusseldorf 2017
Session: Service Workers
When: 2017-05-13 11:00
How to get a service worker running Step 0: HTTPS Step 1: Write your service worker
'The way to think about it is launching a MITM attack on your own site.'
It's a set of instructions where the browser has to look for the files of your site. It intercepts requests.
What are good things to use this for IndieWeb? Nobrainers:
- Having an offline page with basic contact
- Caching static assets (JS, CSS)
- Offline Index: "You're offline, but here's what we've cached'.
- Lie-fi (crappy connection)
- Race cache vs network
- In some (crazy good) network conditions, the network response is faster than the cache response
- Queing (non GET-requests)
- post notes via an HTML-form, intercept with ServiceWorker, no connection, so post it when you're back online (next time you visit the page).
- 'service worker side rendering': render only the diffs
- Glenn (citation needed) has an approach where he uses the cache to store css selectors (via virtual urls) into the cache. Since the cache api is accessible from the browser (where a dom exists) a browserside js can then read partials from that cache (via the virtual urls) and update these partials on the page.
- Background sync
The creepyness of service workers
- When an offline page tells you 'i know exactly what pages you browsed on my site'
- When an iframe on pagea.com to pageb.com loads a whoooole lot of content from pageb.com
Boilerplates / Tools / Input
- Google's SW-Toolbox