[AMPLIFY]: Introducing Enhanced Content Safety Features on Openverse

[AetherUnbound]

What is the goal of this amplification request? (select all that apply)

Inform community/make an announcement (no action necessary), Solicit feedback

What is the intended audience(s) for this content? (select all that apply)

General WordPress community, WordPress users (existing), WordPress users (new/potential)

Are there any specific platforms where you would like this to be shared? (select all that apply)

Any/All/Don't know

Campaign

None/Not sure/Other

MakeWP Team

Openverse

What do you want to amplify?

We'd like to share new sensitive content browsing features which are available in Openverse.

Amplification request details

The details of the features that are available are present in the linked P2 on our blog. While Openverse has always been filtering content that was reported by users, this new feature filters media that has sensitive textual content within it. It also allows users the ability to enable viewing sensitive results.

Links

https://make.wordpress.org/openverse/2023/12/11/introducing-enhanced-content-safety-features-on-openverse/

Deadline

No response

Additional important dates

No response

Any additional notes or details? If you marked "Other" above, please provide additional details here.

No response

[bjmcsherry]

Copy has been written for this, but with character spacing at a premium, I wanted to share it here before publishing. @AetherUnbound, is this okay?:

Openverse has introduced a significant update with new features to filter sensitive content. By default, openly licensed media that contain sensitive content are now excluded from search results, ensuring an accessible and safer browsing experience: https://make.wordpress.org/openverse/2023/12/11/introducing-enhanced-content-safety-features-on-openverse/

[AetherUnbound]

Thanks @bjmcsherry! I would only modify

By default, openly licensed media that contain sensitive content are now excluded from search results

To

By default, openly licensed media that contain sensitive textual content are now excluded from search results

We already exclude known sensitive content by default, this new feature adds additional filtering based on the title/tags/description of the work! Would that sound okay?

[rmartinezduque]

@bjmcsherry, what do you think about this copy option to incorporate @AetherUnbound's feedback while staying within the allowed characters?

✨ Introducing new features for enhanced content safety on Openverse. By default, search results now exclude openly licensed media containing sensitive textual content—with the ability to adjust this setting based on your preferences: https://make.wordpress.org/openverse/2023/12/11/introducing-enhanced-content-safety-features-on-openverse/ #WPOpenverse

[bjmcsherry]

@rmartinezduque That works for me. @AetherUnbound Does the above copy from Reyes, work for you?

[AetherUnbound]

That sounds perfect!

[bjmcsherry]

Perfect. I will move forward and build out the campaign for us.

[bjmcsherry]

This Campaign has been built and will deploy over the next hour on LinkedIn, Twitter/X, Facebook, and Instagram.

[AetherUnbound]

Thanks folks!

[rmartinezduque]

These are the links to the social posts:

• X/Twitter
• Facebook
• LinkedIn
• Instagram