One of the Social Web Foundation’s programs for this year is to work on making [long-form text](https://socialwebfoundation.org/long-form-text-on-the-fediverse/ ) more useful and available on the Social Web. By this, we mean multi-paragraph texts of “web page” length, like a blog post, a magazine article, a newsletter, a forum post, or a wiki page. This length of text can *usually* fit comfortably into a single ActivityPub object — let’s say tens or maybe low hundreds of kilobytes of content. Longer texts like books are probably too big for this use.
There are a lot of producers of long-form text on the Web, and many have enabled ActivityPub for their software. There is some discussion of longer texts in the [Activity Vocabulary](https://www.w3.org/TR/activitystreams-vocabulary/ ) — the definition of most of the data types used in ActivityPub — but it’s not all in one place, and there’s not practical guidance on restrictions.
To help publishers and consumers of long-form text objects, I pulled together the relevant properties and types into a [Fediverse Enhancement Proposal](https://codeberg.org/fediverse/fep ) (FEP), which is a community-led standardization process. The document, [FEP-b2b8: Long-form Text](https://codeberg.org/fediverse/fep/src/branch/main/fep/b2b8/fep-b2b8.md ), is currently available as a draft for review.
If you’re a publisher of long-form text, or you are developing user interfaces that may encounter this kind of data, please take some time to review. This is still a draft-level document, but I’d love to see it shaped and improved by incorporating the experience and knowledge of many practitioners and implementers.