{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifdoudzkadxsw3iwqss6nceuu3frztihjpa2giqrzxw5yczgx7uc4",
    "uri": "at://did:plc:t33vcfaezw7iwyoz7xiejurq/app.bsky.feed.post/3mo5zy4sor2r2"
  },
  "path": "/t/authorizing-for-crossposting-results-in-a-502-on-micro-blog/4365#post_1",
  "publishedAt": "2026-06-13T03:32:15.000Z",
  "site": "https://help.micro.blog",
  "tags": [
    "https://micro.blog/mastodon/callback"
  ],
  "textContent": "Connecting a Mastodon account on signers.online (Mastodon 4.6.0-rc.1+glitch) fails: micro.blog’s /mastodon/callback receives the OAuth authorization redirect but never POSTs to /oauth/token to redeem the code.\n\nOn signers.online’s side the app is registered correctly (redirect_uri https://micro.blog/mastodon/callback, scopes read write follow), /oauth/authorize returns 302 with a valid code in ~30 ms, and /oauth/token is healthy.\n\nAcross ~10 attempts signers.online issued 10 authorization codes; micro.blog redeemed exactly one, and that token was then never used for any API call.\n\nThe callback appears to error (502) before redeeming the code.",
  "title": "Authorizing for crossposting results in a 502 on micro.blog"
}