{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifgkdsojquczgx3usxhnfabngjvfhmdkqcaubq6ggd22szwb2tq2u",
    "uri": "at://did:plc:o6qifsilah5xuggjc2oo3a6d/app.bsky.feed.post/3mna432yaxbz2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreih3oh7mio6yzec6sid2tnuxkqhfcorq6ea75q4rzdmnagjlosmmtq"
    },
    "mimeType": "image/jpeg",
    "size": 11919
  },
  "path": "/2026/06/01/001757.html",
  "publishedAt": "2026-06-01T04:17:57.000Z",
  "site": "https://www.timothychambers.net",
  "tags": [
    "Standard.site",
    "https://atproto.com/blog/standard-site-bluesky-timeline"
  ],
  "textContent": "I’m experimenting with this UX: Saw the post that BlueSky is now supporting longer form articles using Standard.site. Which I thinks is only good. But might it become “double plus good” if this same UX could make it so that posts that were say 500 characters, or more authored on one platform, could “POSSE” over to Bluesky in this new Standard.site mode and not just look like a link card, but as as a decent microblog post with the rest of the thread continuing in the full article.\n\nNot sure it will work well from a user expectation level, but worth a try.\n\nHere is an article about the new support for longer form articles on Bluesky: https://atproto.com/blog/standard-site-bluesky-timeline",
  "title": "BlueSky, Standard.Site and Cross-Posting"
}