The end
b5 (@b5.bsky.social)
Ok, a rundown of how we get p2p ATProtocol going: 1. Run *standard* ATProto services, locally 2. Use p2p to holepunch TCP connections 3. Add a thin layer for peering management Bundle all that up in an app, and we have a recipe for adding resilience & scaling to Bluesky. 🧵 teim:
Village-scale resilience
The end-of-the-world already happened, it's just not evenly distributed. But with every end is a new beginning.
Building more resilient local-first software with atproto – Day 1 – Local-First Conf 2026
The world's first and best event dedicated to local-first software.
Groundmist
atproto for local-first publishing
Exploring an effortless private to publishing pipeline for local-first software leveraging the AT Protocol’s global distribution.
Mitigating Geopolitical Risks with Local-First Software and atproto
Martin Kleppmann discusses the urgent need for technological sovereignty in modern infrastructure. Exploring the shifting landscape of global tech dependencies, he shares how engineering leaders can leverage multi-cloud architecture, de facto API standardization, the AT Protocol, and local-first development paradigms to reclaim user agency and build highly resilient systems.
Building More Resilient Local-First Software with atproto | jakelazaroff.com
atproto has the potential to become a rock-solid replacement for the most fragile part of any local-first app: the sync server.
Exploring CRDT Lexicons
I’ve (alongside many others I’m sure) been working on CRDT work with atproto, and I think we’ll need to come up with some standard for how to represent CRDT data as lexicons. @chris.pardy.family has written a leaflet exploring what such a record could look like and is looking for feedback and thoughts: CRDT's on ATProto I think it’s a good start. It doesn’t tie us to any particular CRDT, though it doesn’t guarantee interop between different CRDT types, which seems fine to me. I’m thinking may...
CRDT's on ATProto
Announcing Skyboard - A collaborative kanban board on the AT Protocol
Skyboard is a collaborative kanban board on the AT protocol so you control your boards forever.
Collection
Updated 2mo
particularly excited about this because webrtc data channels mean you can add just about any p2p functionality. for example, you could get around the latency issues with my yjs demo by exchanging updates peer-to-peer rather than using the firehose.
Jake Lazaroff
couldn't make it to #atmosphereconf so i've been cooking at home instead i'm pretty excited about this one: a way to build real-time collaborative apps with *no dedicated sync infrastructure* — just some static files and atproto