@mfossati @APizzata-WMF can this be easily done in the image suggestion pipeline?

This is something that needs to happen in the pipeline. Moving it to tracking for Growth, because it also affects what images are presented in the Growth Add-an-Image newcomer task.

@Ahoelzl TL;DR: not easy.

Besides a tag that my former team introduced on Commons UploadWizard, I'm not aware of other methods to mark uploaded content as AI-generated:

Looping in @Cparle, as I might have outdated information on AI-generated content handling on Commons.

In T422513#11813943, @mfossati wrote:

IIRC those tags live in the wikitext of Commons File pages, so parsing becomes a requirement

Specifically, the tag adds the PD-algorithm template.

Looping in @Cparle, as I might have outdated information on AI-generated content handling on Commons.

I don't know anything more than what you're posted above ¯\_(ツ)_/¯

fwiw the image mentioned in the task also has a structured-data claim of "instanceof : AI-generated image" (Q116177346). Although this was added manually, could it be part of the pipeline for selecting or filtering images?

@GGoncalves-WMF who is the product owner of image suggestion generation logic? I think DPE has agreed to own the pipeline maintenance. In order to make this task actionable, someone has to do a lot of work to figure out the right thing to do for the product.

In T422513#12304715, @Ottomata wrote:

@GGoncalves-WMF who is the product owner of image suggestion generation logic? I think DPE has agreed to own the pipeline maintenance. In order to make this task actionable, someone has to do a lot of work to figure out the right thing to do for the product.

Originally the Growth team worked with the Structured Data/Content team to define image generation logic. Now that there is no Structured Content team, I imagine Growth's PM is the owner (hi, it's me!).

From the product perspective, I think it's likely best to just avoid suggesting AI-generated images across all wikis. Individual wikis can decide they are OK for certain articles, but for a cross-wiki tool, I think it's safest to assume we should avoid surfacing them as suggestions since newcomers are unlikely to know their local wiki rules on this topic.

If we agree with that direction, this solution seems like the most ideal one:

filter images with the {{PD-algorithm}} template in their Commons File pages

I realize, though, that this isn't a particularly easy change. So I’m curious whether this complaint has come up repeatedly, and how urgent we think it is. I know it came up once after a bad edit, but my impression was that this has been a relatively rare issue.

That said, now that we’re unblocked in scaling Add an Image and could potentially scale this task more widely, I wonder if this could become more visible and therefore more important to address.

Agree with Growth as product management owner.

In previous discussions on DE onboarding image suggestions, I think we were headed in the direction of Growth owning the product roadmap and requirements, with the pipeline itself still a bit fuzzier/co-owned between Growth and DE, to be further fleshed out when a product improvement came up. Since then we've started using the Service Catalog ownership model in other projects, and can probably try to formalize things in that framework.

All of that is to say: Kirsten, if this is a priority, we can partner on this.