In fact, one of the leading local-first libraries, Zero, doesn't even fully support offline: zero.rocicorp.dev/docs/offline They only support offline reads, the same as Count Cachula! So I ask, if fast instant reads is the goal, isn't standard HTTP caching mechanisms the better way to go?
Offline
zero.rocicorp.devNov 18, 2025 at 1:23 PM
Zero is Not Local-First. It's Better.
Zero's partial sync approach gives us more control, better performance, and fewer headaches when building apps with lots of data. Here's why, and how I've been using it.
Speed up your Nix Flake builds & caching with Devour-Flake & Cachix
I put together a guide on how to make your Nix flake builds and caching a lot faster using devour-flake alongside Cachix, and I wanted to share it…
Launching QuickDID - Fast, Open Handle Resolution for the AT Protocol - Nick's Blog
QuickDID is a high-performance, open source handle resolution service for the ATmosphere that serves as both public infrastructure at https://quickdid.smokesignal.tools and deployable software under MIT license. It offers flexible caching strategies (memory/Redis/SQLite), scales from single-instance to distributed deployments, and includes production features like rate limiting and proactive cache refresh. Currently a release candidate, it provides a drop-in alternative to Bluesky's resolver while giving developers full control over their handle resolution infrastructure.
Fresh 2.3: Zero JS by default, View Transitions, and Temporal support | Deno
Fresh 2.3 ships true zero-JS pages, View Transitions, CSP nonce support, IP filtering, and Temporal API support in islands.
An inside look at gRPC - performance, testing and load balancing, Mon, Jul 22, 2024, 6:00 PM | Meetup
Agenda: 5:30 Doors open 6:00 - 6:05: Announcements 6:05 - 6:30: The rest of the iceberg: performance and testing of the gRPC libraries - Ashley Zhang and AJ Heller 6:30 - 7
quick_cache - Rust
Lightweight, high performance concurrent cache. It allows very fast access to the cached items with little overhead compared to a plain concurrent hash table. No allocations are ever performed unless the cache internal state table needs growing (which will eventually stabilize).
Cross-Origin Storage API: Stop Downloading Twice
The Cross-Origin Storage API lets sites share one cached copy of a file (a JS library, font, or AI model) across origins by SHA-256 hash. Here's how it works.
the critical thing that got me on board with atproto is relays incrementalize sync of the entire dataset, which eliminates polling when crawling the old web is currently being crushed under crawler load and I don't think it's going away, so I think atproto is the only way to save the open web
@infra.coop (alpha) img cdn, optimization, transformations, edge caching for 30 days, 15 day revalidation, atproto-native, subscribes to firehose for account deletion to purge user blobs 192 imgs loaded, 156mb vs 19mb, 88% less data, 1.7x speed up (in this test) github.com/co-infra/co-infra-img
@dholms.at can we fix that? iirc the rate limit headers RFC allows them on all responses? (Though obviously caching GET at CDN might skew things)
alice
i love services that are rate limited but also do not publish their rate limits in headers i'm looking at you plc.directory
