Skip to content

Sexually-orientated -> Sexually explicit in policy text#599

Closed
rollerozxa wants to merge 1 commit into
luanti-org:masterfrom
rollerozxa:patch-3
Closed

Sexually-orientated -> Sexually explicit in policy text#599
rollerozxa wants to merge 1 commit into
luanti-org:masterfrom
rollerozxa:patch-3

Conversation

@rollerozxa

Copy link
Copy Markdown
Member

"Sexually-orientated" feels oddly worded and I think it's generally more common and clear to call it "sexually explicit" when forbidding pornographic content and such.

@appgurueu

Copy link
Copy Markdown
Contributor

Seems fine by me, though the implication would be that "sexually implicit" content (e.g. sexual innuendo) is permitted. Should it be? I don't know.

I agree that the current wording is weird though (and even vaguely sounds like the kind of language that would be used to ban stuff like pride flags).

@rollerozxa

rollerozxa commented Jun 17, 2025

Copy link
Copy Markdown
Member Author

Seems fine by me, though the implication would be that "sexually implicit" content (e.g. sexual innuendo) is permitted. Should it be? I don't know.

Well swearing is allowed (also see the bad_language content warning) and a lot of swearing is just sexual innuendos. The rule is just meant to align ourselves with the ToS of the cloud provider that hosts ContentDB (netcup), which only mentions the following as being disallowed:

Actions intended to store and provide access to material of a pornographic or commercially erotic character

@rubenwardy

rubenwardy commented Jul 1, 2025

Copy link
Copy Markdown
Member

The OSA language is:

Pornographic content. This includes content of such a nature that it is reasonable to assume that it was produced solely or principally for the purpose of sexual arousal.


be that "sexually implicit" content (e.g. sexual innuendo)

Something like "woo hoo" in the sims would be allowed. It's more about graphic (visual or text) content that would cause issues with OSA or hosting providers

@rubenwardy

Copy link
Copy Markdown
Member

Closing in favour of #601 which just links to the TOS document

@rubenwardy rubenwardy closed this Jul 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants