Tailscale-as-a-service via AT Protocol (Bluesky) identity — isolated mesh networks with invite-by-handle
Decentralised Identity 🤝 Mesh Networking - Thinking with portals
How you can invite your Bluesky friends into your Tailscale network using an OIDC shim
ATsense: ATproto-style Federation for Open Sensor Networks (Draft)
ATsense: ATproto-style Federation for Open Sensor Networks (Draft) · GitHub
Introduction to AT Protocol
Walkthrough of the various parts and concepts in Bluesky's AT Protocol (ATProto), the types of servers involved and how it all fits together
Introduction to AT Protocol
Walkthrough of the various parts and concepts in Bluesky's AT Protocol (ATProto), the types of servers involved and how it all fits together
atproto.energy
Energy networks built on open protocols — from a Bluesky post about AI emissions to a case for open protocols in the energy sector, built on the AT Protocol.
tijs/atproto-oauth
Framework-agnostic OAuth integration for AT Protocol (Bluesky) applications
Understanding Atproto - AT Protocol Docs - AT Protocol
Dive deeper into the concepts behind the AT Protocol.
Service Auth | Bluesky
There are currently two "types" of auth supported in the atproto network: client-server auth and service-to-service auth.
Creating the Internet Layer That Should Have Been With Avery Pennarun
aTIProto — ATProto-native Payments
aTIProto is an ATProto-native payments protocol. Build payments, subscriptions, and pay-what-you-want experiences on the Bluesky network.
ATPROTO isn’t just for Bluesky weiners
OAuth for AT Protocol | Bluesky
We are very happy to release the initial specification of OAuth for AT Protocol! This is expected to be the primary authentication and authorization system between atproto client apps and PDS instances going forward, replacing the current flow using App Passwords and createSession over time.
Meshtastic
An open source, off-grid, decentralized mesh network built to run on affordable, low-power devices
TIL: Iroh: peer-to-peer networking for app developers
I came across Iroh (via, via) today as it hit 1.0 and found it a really interesting solution to a problem I knew existed but had not thought a lot about. Judging from the comment sections, it seems pretty clear that lots of people are confused as to exactly what Iroh is. I don’t think their launch post does their product justice at all, and their tagline is “IP addresses break, dial keys instead” which sounds cool, but if you think about it for just a second, you’ll end up with lots of questions. The biggest one is: “so how is this different from a mesh VPN like Tailscale, ZeroTier, Netbird, etc.?” It’s only after reading a lot of developers’ comments on the threads that I feel I understand: Iroh is aimed at application developers who want to communicate P2P between machines running their app, while mesh networks are aimed at network admins who want to connect devices they own/manage together.
I wrote up my talk at @localfirstconf.com as a blogpost The AT Protocol is a high-scale network by design. It works by codifying proven architectures into a protocol. If you've ever used kafka to connect some backend services, then you basically know how atproto works.
Starting from scale in the design of the AT Protocol
pfrazee.leaflet.pub