Hacker News new | ask | show | jobs
by ForHackernews 852 days ago
"I want a model that recognizes faces, but I didn't train it on enough black faces" => not-racism, according to you.

"I want a model that produces racially diverse images of people, but I didn't test it in racially homogenous historical contexts" => yes-racism, according to you.

2 comments

> "I want a model that produces racially diverse images of people, but I didn't test it in racially homogenous historical contexts"

You are again misrepresenting the OP. If you go actually read the OP you will find it very clearly describes Google's initial steps towards fixing the problem, which was: double down on race-swapping in historical contexts. The OP very clearly (and correctly) argues that this is not the action of a person who goes "oops forgot to test in this context" but is rather the action of a person who very intentionally wanted the image generator to behave this way in this context.

Did the developers intend their product to manipulate race in its outputs or not? It's a simpler question than these contorted reformulations you present.

But probably not simple enough to pierce ideological bias. I'll ask instead: you really believe that it wasn't tested in historical and other contexts where white people were erased?

> I'll ask instead: you really believe that it wasn't tested in historical and other contexts where white people were erased?

Occam's Razor: Of course it wasn't or they wouldn't have released such a ridiculous embarrassing product! C'mon, I think you're the one wearing blinders here.

We'll see what comes out later, but I give it 90:10 odds that this behavior was seen in testing and accepted by developers/DEI commissars - the failure was in not forseeing the reaction of the non-DEI-extremist public.

Of a piece with 'Google more or less explicitly said I won't be promoted because I'm White' stories.

> Of course it wasn't or they wouldn't have released such a ridiculous embarrassing product!

Then please do explain why their first reaction was to double down on "diversity" in historical contexts, before eventually retreating?

Because adding the word "diverse" to the text of to their output is a lot easier than retraining their model? They're always going to try for the easy fix first.

Have you never tried tweaking the error text first before giving up and redesigning your form that's confusing users?

Hmmh. Fair enough. I didn't think about it from the perspective of "error text", but now that I think in that mental model, I think you're right here.