{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib4pnja3unx3o7r47ihs5dm5ipitwdj5a3yeamullbnwilftls4ky",
    "uri": "at://did:plc:ixd3llanirxy6by2epvxdu7k/app.bsky.feed.post/3mfp3ynhvsew2"
  },
  "description": "NodeBB federates out `Note` or `Article` depending on the length of the content. While this by-and-large works, the article logic does not encourage as much discussion as expected because a `summary` is generated so as to provide something for microblog-style software to show (otherwise, it would only show the title (`name`) and a URL to the forum.)\n\nThat summary is limited to a maximum or 500 characters, ending at the last full detected sentence.\n\nWhen composing a long topic, 500 characters may not be enough to fully introduce the topic and engage users. This lowers click-through rates.\n\nI expressed my frustration about this online to @thisismissem and suggested that I might just revert back to sending the entire post content in `summary`. This would violate FEP b2b8's recommendation that summary be a maximum of 500 characters:\n\n> It should be a maximum of about 500 characters; a few sentences; or a short paragraph.\n\nAfter consultation with Matt Baer of Writefreely (@matt@writing.exchange), he suggested the following changes:[...]",
  "path": "/post/1350",
  "publishedAt": "2026-02-25T16:26:03.214Z",
  "site": "https://activitypub.space",
  "tags": [
    "article",
    "longform",
    "b2b8",
    "fep",
    "@thisismissem@activitypub.space",
    "@matt@writing.exchange",
    "@evan@activitypub.space",
    "@evan@cosocial.ca",
    "FEP b2b8's recommendation",
    "@evan"
  ],
  "textContent": "NodeBB federates out `Note` or `Article` depending on the length of the content. While this by-and-large works, the article logic does not encourage as much discussion as expected because a `summary` is generated so as to provide something for microblog-style software to show (otherwise, it would only show the title (`name`) and a URL to the forum.)\n\nThat summary is limited to a maximum or 500 characters, ending at the last full detected sentence.\n\nWhen composing a long topic, 500 characters may not be enough to fully introduce the topic and engage users. This lowers click-through rates.\n\nI expressed my frustration about this online to @thisismissem and suggested that I might just revert back to sending the entire post content in `summary`. This would violate FEP b2b8's recommendation that summary be a maximum of 500 characters:\n\n> It should be a maximum of about 500 characters; a few sentences; or a short paragraph.\n\nAfter consultation with Matt Baer of Writefreely (@matt@writing.exchange), he suggested the following changes:[...]\n\n  * Append a `[...]` at the end of the truncated content to signal that there is additional content that is not seen\n  * Allow the use of a magic string (like an HTML comment: `<!-- break -->`) that would allow power users to manually select where the summary should end. This would still allow for summaries over 500 characters.\n\n\n\nThat seems like a good compromise for me, where concerns from power users like myself would be addressed, while not overly complicating the interface for users who do not need to know about this.\n\nPinging @evan (@evan\" aria-label=\"Profile: evan@cosocial.ca\">@evan@cosocial.ca) for his thoughts.",
  "title": "Reduced engagement due to Article type",
  "updatedAt": "2026-02-27T02:07:49.344Z"
}