Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think a lot of the motivation for running it in the cloud is so they can have a single point of control for enforcing editing policies (e.g. swapping faces).


Do you have evidence of that? Photoshop has blocked you from editing pictures of money for ages and that wasn't in the cloud. Moreover, how does a Google data center know whether you're allowed to swap a particular face versus your device? It's quite a reach to assume Google would go out of their way to prevent you from doing things on your device in their app when other AI-powered apps on your device already exist and don't have such policy restrictions.


When I try to remove the head of a person using Magic Editor, I get the message "Magic Editor can't complete this edit. Try a different edit." Also documented here: https://www.androidauthority.com/google-photos-magic-editor-...

I have no doubt Google could (and might) enforce a lot of these rules on the device, but they likely route it through the cloud if there's a new "exploit" that they want to block ASAP instead of waiting for the app to update.

This is an example of the reputational risk Google has to deal with that small startups don't. If some minor app lets you forge photos, it's not a headline. If an official Google app on billions of devices lets you do it, it's a hot topic.


It could simply also be that their inpainting model is quite bad at certain things, and replacing a person's head produces consistently bad results. Hiding the problem could simply be easier than fixing it.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: