{
  "$type": "site.standard.document",
  "description": "Build support for AT Protocol Authorization directly into IO.",
  "path": "/decisions/atproto/",
  "publishedAt": "2025-03-22T00:00:00Z",
  "site": "at://did:plc:bnr33h7nafe5nk4zzlshvana/site.standard.publication/3mnb3xdhll227",
  "tags": [
    "OAuth",
    "AT Protocol",
    "IO"
  ],
  "textContent": "At the Atmosphere Conference , it seemed clear that the ATProtocol variant of OAuth was a big challenge for application developers and was something that could provide a lot of value if it was provided by a proxy. Pros ATProto OAuth is hard! Lots of developers won't want to do it. Clients that can rely on a proxy are much simpler. A proxy can support clients written in any programming language. Cons ATProto OAuth is hard! This took several weeks of work. Some developers will prefer to have this in their code. An authenticating proxy ( AIP ) has already been released. ",
  "title": "Build AT Protocol OAuth Support"
}