(no title)
kevdoran | 6 months ago
Even published a very cool article last July about all the (considerable) challenges one runs into when going after making wasm-sqlite work: https://www.notion.com/blog/how-we-sped-up-notion-in-the-bro...
kevdoran | 6 months ago
Even published a very cool article last July about all the (considerable) challenges one runs into when going after making wasm-sqlite work: https://www.notion.com/blog/how-we-sped-up-notion-in-the-bro...
jitl|6 months ago
It would "mostly work" offline before, but you could have cases where some blocks in a page aged out of the LRU, or they changed online in a way that invalidated the page but new content wasn't downloaded. When that happens we show a "go online to view" error instead of risking you viewing/editing a known-incorrect local snapshot of the page.
With "available offline", we now proactively download and keep up-to-date the content you want available offline. It will either work, or show an explicit error if things go wrong in the sync process. No more guesswork.