8000 Content Warnings · Issue #232 · w3c/activitypub · GitHub
[go: up one dir, main page]

Skip to content

Content Warnings #232

@cwebber

Description

@cwebber

Mastodon has Content Warnings and they seem like a pretty good idea. Currently, it looks like Mastodon will implement Content Warnings using the summary field which is pretty clever.

Previously I thought / assumed that Content Warnings could/would be done on the tag property with a special type, like {"tag": [{"type": "ContentWarning", "content": "American Gods spoilers"}]} but maybe this summary solution is a better idea. Maybe we should still keep the "ContentWarning" type in there, I dunno?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0