Feature #19192
closed
Added by Laurie Hurson about 1 year ago.
Updated about 1 year ago.
Category name:
WordPress Plugins
Description
Hi All,
I was creating a post and noticed that I had options to "Ask the AI Assistant". (!!) See screenshots.
"AI Assistant (Experimental)
Automatically generate and modify content, powered by AI magic.
The AI Assistant can be imprecise with information about people, places, or facts.
We are experimenting with this feature and can tweak or remove it at any point."
I think this is an experimental feature through Jetpack but wanted to flag it. I don't know if we can opt out of the AI assistant aspect of jetpack or turn it off? But I thought we should know this is happening and discuss as our users will likely see this.
Files
The AI Assistant block, I think, is added by the Jetpack plugin. So far I have found that it wil generate content - you can pose prompts and it will write post content. Or, you can ask to create specific types of content. You can also highlight already written content in the editor and ask it spell check, expand, summarize.
Its likely that only sites with jetpack enabled will be able to see this block, but I do think we might consider disabling it for sites with jetpack if possible? Its possible that having this block sends the message that the Commons support AI generated writing - what do others think?
Oof. Yeah, I would be in favor of turning this off if possible.
Jetpack 12.8 will introduce a filter allowing us to turn off the AI assistant. However, Jetpack 12.8 isn't out yet; it's scheduled to be released on November 7th. We can look into updating Jetpack as part of the next maintenance release on the 14th, but we usually do major plugin updates at the end of the month.
When we upgrade to Jetpack 12.8, we'll need to add the following code snippet to disable the AI assistant:
add_filter( 'jetpack_ai_enabled', '__return_false' );
The alternative is writing some javascript to hide the AI Assistant block using the following JS filter: https://developer.wordpress.org/block-editor/reference-guides/filters/block-filters/#blocks-registerblocktype
I've had to use the JS approach before to hide certain Gutenberg blocks for another project, so we can do that as well if desired.
Up to you, Ray. I think we can probably wait five days if that's what it takes. Or, if it wouldn't be a big deal to write the JS needed, please do. thank you
- Assignee set to Raymond Hoh
I don't understand why the Jetpack team would roll this out as a non-toggleable feature. I can imagine someone on the Commons enjoying this feature, but we are forced to either leave it on for everyone, or turn it off for everyone.
Anyway, Ray, I think it's probably good to roll out a JS-based solution right away as a hotfix, as this feature is likely to befuddle many of our users. We can also put the PHP filter in place and roll back the JS fix at the end of the month.
Thanks so much for the feedback and ideas. I think it makes sense to use the JS to turn off the feature for now.
- Category name set to WordPress Plugins
- Status changed from New to Staged for Production Release
- Target version set to 2.2.2
- Status changed from Staged for Production Release to Resolved
Also available in: Atom
PDF
