Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Sensitive Media" tag #231

Closed
cwebber opened this issue Jun 18, 2017 · 15 comments
Closed

"Sensitive Media" tag #231

cwebber opened this issue Jun 18, 2017 · 15 comments

Comments

@cwebber
Copy link
Collaborator

cwebber commented Jun 18, 2017

Is there a proper way to mark something as NSFW? Is this important enough to have in ActivityPub proper, or should it be an extension?

See also this thread on NSFW in AP + Mastodon.

@nightpool
Copy link
Collaborator

nightpool commented Jun 18, 2017

side note: Can we refer to it in discussions going forward as "sensitive media"? (and rename the issue?) NSFW is mostly used as a historical accident, and it has weird implications, is hard to localize, and is rooted in bad workplace culture assumptions (including assumptions about sex work)

@nightpool
Copy link
Collaborator

nightpool commented Jun 18, 2017

Anyway, I think the correct way to do this is to add a "sensitive" boolean property to Image, Video, and Audio. (or perhaps a string ("warning"?) that can contain a specific warning about the content if one exists.)

@cwebber cwebber changed the title NSFW tag "Sensitive Media" tag Jun 18, 2017
@cwebber
Copy link
Collaborator Author

cwebber commented Jun 18, 2017

side note: Can we refer to it in discussions going forward as "sensitive media"? (and rename the issue?)

Good call, and done.

@cwebber
Copy link
Collaborator Author

cwebber commented Jun 18, 2017

Anyway, I think the correct way to do this is to add a "sensitive" boolean property to Image, Video, and Audio.

Good call, and I think there's no need to restrict it based on object type. There's all sorts "sensitive" literature out there :)

@cwebber
Copy link
Collaborator Author

cwebber commented Jun 20, 2017

We're thinking related to #232 there would be a common Content Warning type tag for sensitive media.

@ghost
Copy link

ghost commented Jun 20, 2017

We had this same discussion about email back in the 80s. A simple boolean wasn't seen as enough information; as some people are sensitive to different things. This wasn't ever implemented but we ended up in general agreement on an enum or tag set which could reference the concepts of soft-nudity, porn, violent content, and religious polarisation. Actually I seem to recall there ended up with about 20-30 categories and a lot of bickering over details and that's likely why the discussion died, but these were the ones that I personally took to be critical. For instance alcohol is offensive to some, but this is often seen by others as a subset of religious polarisation. You also have completely different interpretations of soft-nudity across cultures.

@cwebber
Copy link
Collaborator Author

cwebber commented Jun 21, 2017

There's strong desire expressed from the Community Group to have this as a new property in ActivityPub, a sensitive property which is a boolean. This can be attached to toplevel objects, or even attachments of images/video etc.

This can be used in addition to content warnings, tags, etc.

@evanminto
Copy link

Should sensitive be used alongside summary then? Like, summary takes on the Mastodon-esque "content warning" connotation when the object is marked as sensitive?

@nightpool
Copy link
Collaborator

nightpool commented Jun 21, 2017 via email

@cwebber
Copy link
Collaborator Author

cwebber commented Jun 27, 2017

@evanminto That would make a lot of sense to me!

@tantek
Copy link
Member

tantek commented Jun 27, 2017

Is this just an advisory flag from the author?

@nightpool
Copy link
Collaborator

nightpool commented Jun 27, 2017 via email

@cwebber
Copy link
Collaborator Author

cwebber commented Jul 25, 2017

We had a resolution recently that ActivityPub won't add properties to ActivityStreams that aren't protocol related, so this needs to move to an extension.

@cwebber
Copy link
Collaborator Author

cwebber commented Aug 27, 2017

Sensitive property proposed here, raising to discuss in next SocialWG and SocialCG calls.

@ThisIsMissEm
Copy link

Sensitive property proposed here, raising to discuss in next SocialWG and SocialCG calls.

What was the eventual outcome here? It looks like it's an extension that's used but not documented in any spec or namespace officially.

i think the landscape may also have changed significantly since 2017, wherein publishing sensitive content (especially adult content) to persons under the age of 18 is now an offence that can carry fines & jail time (see age verification bills around the world, Germany, France, several US states, the UK, Australia, etc). These laws actually mandate verifying a user is over the age of 18 (sometimes dubbed the PG-ification of the internet, where everyone is assumed to be a child until otherwise proven)

Back in 2018, for Switter to exist on the fediverse, that instance had to mark all outgoing media as sensitive (as what's sensitive to different groups is contextual, and majority of the content moderation reports were from people seeing adult content in the federated timeline, but it not being marked as sensitive).

There's also now tumblr's new content labelling which seems to be at the behest of Apple, which categorises into Mature or not, and within Mature, several categories (alcohol & drugs, violence & gore, sexual themes).

Given the growth of the fediverse, and the change in the political/legal landscape, is there a need to revisit the definition of "sensitive content"?

Or would this be better addressed through custom audiences or groups? (e.g., users' could mute posts targeting a specific audience, but still get the rest of that users posts that don't include that audience?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants