social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

479
active users

#serviceworker

0 posts0 participants0 posts today

“A Local-First Case Study” by @jakelazaroff

🔗 jakelazaroff.com/words/a-local

> It helps a lot that various libraries in the ecosystem compose well. Just snapping together ProseMirror, Yjs and Y-Sweet gave me a collaborative rich text editor with shared cursors. Adding in `yjs-indexeddb` made it work offline. This was all mostly out of the box, with very little setup; the degree to which everything Just Works is…

#PWA #ServiceWorker #offline

⚓nicolas-hoizey.com/links/2024/

“Building a Single-Page App with htmx” by @jakelazaroff

🔗 jakelazaroff.com/words/buildin

> It’s a simple proof of concept todo list. Once the page is loaded, there is no additional communication with a server. Everything happens locally on the client.
>
> How does that work, given that htmx is focused on managing hypermedia exchanges over the network?
>
> With one simple trick: the “server-side” code runs in a service…

#ServiceWorker #htmx

⚓nicolas-hoizey.com/links/2024/

“A Local-First Case Study” by @jakelazaroff

🔗 jakelazaroff.com/words/a-local

> It helps a lot that various libraries in the ecosystem compose well. Just snapping together ProseMirror, Yjs and Y-Sweet gave me a collaborative rich text editor with shared cursors. Adding in `yjs-indexeddb` made it work offline. This was all mostly out of the box, with very little setup; the degree to which everything Just Works is…

#PWA #ServiceWorker #offline

⚓nicolas-hoizey.com/links/2024/

“Building a Single-Page App with htmx” by @jakelazaroff

🔗 jakelazaroff.com/words/buildin

> It’s a simple proof of concept todo list. Once the page is loaded, there is no additional communication with a server. Everything happens locally on the client.
>
> How does that work, given that htmx is focused on managing hypermedia exchanges over the network?
>
> With one simple trick: the “server-side” code runs in a service…

#ServiceWorker #htmx

⚓nicolas-hoizey.com/links/2024/

Turbo pet peeve at work is when a customer acts wayyy too familiar. It’s fine if I see you several times a week, or hell! Even once a week! Just some kind of regularity. But I *just* met this dude today and he’s all “where did ya go? I needed a drink and you’re on break!” Like dude idk you like that. Also he needed attention from either me or the other bartender constantly. We got other customers man, don’t worry I’ll be over to listen to your life story after I clear service bar.

@Yoshi @GottaLaff

Sorry not to appreciate her philanthropy properly for you

I've been paying off my #StudentDebt for almost 20 years & barely touched the principal bc I wasn't able to finish my degree & got stuck in low-wage #ServiceWorker positions

It's coming out of #SocialSecurity & part-time library work now

#Capitalism is stupid & I don't gaf if there's one or two nice billionaires out there. Billionaires shouldn't exist while children live in cars

Continued thread

I am really second guessing the decision to build this in #NextJS.

There's a LOT of confusion around the new #AppRouter paradigm, the Discord is a madhouse.

I've been struggling just to get the #serviceWorker and #webmanifest for the #PWA set up right. It seems most people use `next-pwa` but it hasn't been updated to support AppRouter yet so there's a nasty fix to do. github.com/shadowwalker/next-p

I haven't even attempted #ServerComponents yet.

GitHubNext v13 `app-build-manifest.json` - Does not register a service worker that controls page and start_url · Issue #424 · shadowwalker/next-pwaBy jpnws
Continued thread

Hmm, seems like the 500ing is only when I load the page in an incognito window... it's probably still my #workbox cache in the #serviceWorker, but I'm going to replace the `StaleWhileRevalidate` strategy with `NetworkFirst`. This will mean that the page will have to wait for a network response, but it will maintain my offline support so the #PWA install prompt will still appear. #WebDev

Continued thread

First I've got to figure out why my static assets are 500ing half the time. It's probably my slapdash #serviceWorker #caching strategy. I like to use #staleWhileRevalidate because it feels like I should just serve from the #cache if I have *something* but I don't feel like prompting the user to reload if there's fresh data. It's probably a bad UX though. I find myself reloading the page several times just to make sure I'm looking at fresh data.