{
  "path": "/posts/2026-04-29-posse-poster/",
  "site": "https://mike.puddingtime.org",
  "tags": [
    "hugo",
    "posse",
    "publishing",
    "atproto",
    "bluesky",
    "mastodon"
  ],
  "$type": "site.standard.document",
  "title": "POSSE Poster",
  "description": "![Posse Publisher](https://photos.smugmug.com/photos/i-HQrKmJt/0/LZXr6LGG2k85knBRVnRk5n6tP9sBX2PDjbv7M2PdH/L/i-HQrKmJt-L.png)  Well, this has been fun.   1. Start typing. If I exceed 300 characters, I get a color treatment in the editor that tells me so, and a \"summary/Bluesky\" field opens up....",
  "publishedAt": "2026-04-29T00:07:27.721Z",
  "textContent": "![Posse Publisher](https://photos.smugmug.com/photos/i-HQrKmJt/0/LZXr6LGG2k85knBRVnRk5n6tP9sBX2PDjbv7M2PdH/L/i-HQrKmJt-L.png)\n\nWell, this has been fun. \n\n1. Start typing. If I exceed 300 characters, I get a color treatment in the editor that tells me so, and a \"summary/Bluesky\" field opens up. \n\n2. If I keep typing in the editor, I see a character count against hachyderm.io's 2263 character limit.\n\n3. Click `publish` and the post is stashed in my atproto PDS then fanned out to Mastodon and Bluesky. The post is also turned into a git commit for my Hugo blog in an unpublished \"notes\" record.\n\n4. Add a title and click `publish`, and the post is still stored in my PDS, but also turned into a Hugo git commit that kicks off the Cloudflare Pages build for the blog pipeline. \n\n5. Add a photo, it becomes an attachment for Mastodon or Bluesky. If I'm making a blog post, clicking a little clipboard icon lets me add Markdown markup for the SmugMug-hosted version of the image that I can paste into the blog post.\n\nIf I'm making a longish Mastodon post, the Bluesky post stops at 300 characters and includes a link to its longer Mastodon cousin, effectively making my Mastodon account a place for < 500-word posts. If I'm making a Hugo post, Bluesky and Mastodon point to that. All of it is stashed in my PDS and all of it is stashed in Git: One sort of speculative value atproto store, one \"Markdown-n-YAML is forever\" git store. \n\nBecause I'm doing all the image hosting via Smugmug, and all the image links are to Smugmug artifacts, not self-hosted images, posts are more portable. \n\nEnjoy using it? Cool. I can work from this web editor or from a local text editor. \n\nQuit using it? Fine. It all lives as Markdown in git: I still have the same blog, I still have the same accounts, and I forget about this little experiment in exotic publication pipelines. \n\n"
}