standards

<p>Some quick news about the <a href="https://socialwebfoundation.org/long-form-text-on-the-fediverse/" rel="nofollow">Long-form Text</a> project at the Social Web Foundation. After the publication of the draft <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/b2b8/fep-b2b8.md" rel="nofollow">FEP b2b8</a> (“Long-form Text”), the Social Web Foundation has been working with implementers to get more support for the Article data type, representing multi-paragraph text on the Fediverse.</p><p>One of the big pain points has been how subscribers to long-form text from platforms like WordPress, WriteFreely, Plume and Ghost.org see the text in their microblogging platforms like Mastodon or Threads. Often, the data is abbreviated or misformatted. FEP b2b8 is, in part, a way to improve and standardize this problem.</p><p>The work in this area is bearing fruit; a few weeks ago, <a href="https://www.threads.com/@shubhankar_91" rel="nofollow">Shubhankar Srivastava</a> of the Fediverse team at Threads announced that <a href="https://www.threads.com/@shubhankar_91/post/DICyIplp5nz" rel="nofollow">Threads is now properly displaying long-form text from Ghost</a>. This is a big step forward in support.</p><p>The participants in the project are aiming to have better standards support from both publishers and consumers over the next few months, so I’m optimistic that other platforms will see similar improvements.</p> <small class="notice" x-post-type-data="type=&#x27;Article&#x27; attributed_to=None"> Takahe has limited support for this type: <a href="https://socialwebfoundation.org/2025/05/01/steps-forward-in-long-form-text/">See Original Article</a> </small>