Publishers may wish to mark certain content as "sensitive". This can be because the publisher recognizes the content as benefiting from a discretionary warning, or as a courtesy to their audience and their sensitivities regarding certain topics that may be triggering if viewed without a warning. Marking the content as "sensitive" typically hides the content behind a content warning, blurs or collapses media attachments, and requires click-through consent before viewing the content. This approach currently lacks a formally defined processing model for specifying which properties are considered "sensitive" or "content". This document aims to define such a processing model and provide guidance on how sensitive content is handled by publishers and consumers of Activity Streams 2.0 documents, particularly in the fediverse.

For more details on the status of this document, see the following GitHub issues: -

-

TODO: rebase PR https://github.com/swicg/activitypub-trust-and-safety/pull/122/ after the reorganization is merged into main branch