Be advised there may or may not be anything deserving of a warning in the summary field. It's purely a Mastodon convention.
The de facto usage definition comes from the early work on RSS by news organisations in the mid 90s. What they wanted was
title
summary (brief description)
body
Most syndication/federation protocols were built around that model. ActivityStreams maps these to name, summary, and content. Content warnings really belong elsewhere, but this wasn't offered in the AS spec. This might be a good subject for an FEP, so that there's something well-defined to use instead of summary. I for one would adopt it in a heartbeat to get our summary field back.
My advice to @npub1970a95knlckf0kfd3j9ylz5r73v37age804yn4vxfspu7z4r74vqtzwe4s (npub1970…we4s) would be to ignore summary completely on DMs if they don't fit your UX design, but hide images if sensitive is set. People can lose their jobs (or got to jail) over "indecent" images popping up without warning.
mike /
npub1nl…0fh6t
2023-08-24 21:12:17
in reply to nevent1q…h0vr
Author Public Key
npub1nl98j7g9kxkdh5f3u0cxltk8dl0gwt77kxxmk5wtlmstufjrkkqsk0fh6tPublished at
2023-08-24 21:12:17Event JSON
{
"id": "f6f7c984fdb3003d17496163a27d4d32c96b800a424abc1563f3a599ea2a2cb0",
"pubkey": "9fca797905b1acdbd131e3f06faec76fde872fdeb18dbb51cbfee0be2643b581",
"created_at": 1692911537,
"kind": 1,
"tags": [
[
"p",
"2f9fd2d2d3fe2c97d92d8c8a4f8a83f4591f75193bea49d5864c03cf0aa3f558",
"wss://relay.mostr.pub"
],
[
"p",
"657b808e53b524d5a0d0d90c290dfaea781d284ded8f590250ca2b9ed0d8cef5",
"wss://relay.mostr.pub"
],
[
"p",
"9c7c4f0286fb9f22491e71510b51be47be761dc1dc1867fb2390f5921c795446",
"wss://relay.mostr.pub"
],
[
"e",
"2acd8babb2bf00093bc037f9738604b4a0910c7724f238e47f51164faf085043",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://macgirvin.com/item/b860c214-8db1-4141-923a-a421be5adf68",
"activitypub"
]
],
"content": "Be advised there may or may not be anything deserving of a warning in the summary field. It's purely a Mastodon convention. \n\nThe de facto usage definition comes from the early work on RSS by news organisations in the mid 90s. What they wanted was \n\ntitle\nsummary (brief description)\nbody\n\nMost syndication/federation protocols were built around that model. ActivityStreams maps these to name, summary, and content. Content warnings really belong elsewhere, but this wasn't offered in the AS spec. This might be a good subject for an FEP, so that there's something well-defined to use instead of summary. I for one would adopt it in a heartbeat to get our summary field back. \n\nMy advice to @nostr:npub1970a95knlckf0kfd3j9ylz5r73v37age804yn4vxfspu7z4r74vqtzwe4s would be to ignore summary completely on DMs if they don't fit your UX design, but hide images if sensitive is set. People can lose their jobs (or got to jail) over \"indecent\" images popping up without warning.",
"sig": "0a02ce60b11727fcaa2bbfe8b35a332fad67acb8d23d23ad2da78d0cc8b6f1c57aa6161197c5b622e53f48e3e8f6f3f782d3c593e8a65b983d82e9d20126a785"
}