This CloudFlare outage took down Apatosaurus v2, but not for anyone who installed the PWA from their browser

- Notifying the user of their sync status based only on internet access is not sufficient. It might be the case that the server goes down. If so, then the user still needs to be able to do their work but still be notified of the gap in sync.

- The current offline/online status needs to be clearly communicated to the user. "Clearly" being the keyword because in the case of Apatosaurus, there are multiple databases to sync locally. One per transcription document _and_ one for the other metadata.

My working working theory for offline capable apps that do work on data:

- If the app allows editing data offline, then it had better have a robust mechanism for "catching up" when back online.

The candidate will work with my team but be dedicated to a single project. Maybe info: sjobs.brassring.com/TGnewUI/Sear...

That's great!

I would guess it's an indexing bug. Maybe you updated the file, which triggered a reindexing, and instead of replacing that index entry, a new one was appended.

Fantastic!

This is great! Glad you were able to snag the perfect domain too.

I sympathize as I also have to sit out this year.