esullivan@ Thank you for your response, considering this as a feature request and changing the status to untriaged, so that this issue can get addressed.

Thank You...

This could be a neat feature, but the way things are set up, it would be very hard to do using only sync data. Right now the sync types need to be confirmed before priority prefs are even synced. I suppose it's possible you could download the priority pref, have a way to block for that to be applied, and then disable other types before they start configuring. Lots of messy logic.

Trying to place this information in the gaia account or add another round trip to fetch this information as a one off rpc during initialization both sound really bad. We don't want to harm the typical use case for the rare use case.

The benefit is going to be fairly minor as well. All sign in flows should already have ways to fairly conveniently disable specific types from even starting to sync. We could leave this bug open, but in all reality, it would probably never be worked on. I'm going to archive it. If someone wants to do this, feel free to re-open and assign to yourself.