zlacker

Rolling this into Google Docs seems like a nobrainer.

>>tpmx+(OP)
Or rolling this into Google Image Search to create images that match users' search queries on the fly.

Don't like any of the results from the real web? Well how about these we created just for you.

>>tpmx+(OP)
Until they pull of the plug on it.

>>semico+P1
Ah yes, deepfakes porn as a service would have been a blessing for teenage me.

>>tpmx+(OP)
Google is very conservative about anything that can generate open-ended outputs. Also these models are still very expensive computationally.

>>ma2rte+1c
They're expensive to train, but not awfully expensive to use. Especially if you have hundreds of images you want to generate (due to the way compute devices tend to get much more efficiency with a large batch size).

Google could totally afford it, especially if the feature was hidden behind a button the user had to click, and not just run for every image search.

>>london+Sf
The input control is pretty hard - it kinda needs an AGI :). How do you stop undesirable images being created?

>>london+Sf
When diffusion models are used, the inference time could be meaningful. But then this is only 64x64 with upsampling, so probably not too bad.

>>tpmx+oi
If I were running Google, I would release it with a disclaimer, and not do anything technical to prevent undesirable images being created.

How does Adobe prevent Photoshop being used to draw offensive images? They don't... People understand that a tool can be used for good and bad.