Hacker News new | ask | show | jobs
by loxias 1353 days ago
Thanks! I didn't know I could turn that off. I "solved" it by wrapping chrome with my own home grown tooling to maintain multiple parallel profile directories, so I could run "work chrome" and "chrome for gmail" and "chrome for web browsing". Of course, now I use firefox for all 3 so I don't have the problem anymore... :)
2 comments

The flag is long gone, as Google removed it a few release after. I apologize if I didn't make it clear.
It's a setting now. On each browser profile, go to chrome://settings/syncSetup and turn off "Allow Chrome Sign-in".
Its a paranoid reading of the normal launch process.

Behind the scenes every major change like that is a flag that's deployed first off then slowly flipped to default true as a rollout so that it's as low risk as possible of unintended damage / failure.