-
Notifications
You must be signed in to change notification settings - Fork 935
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added support for Google Chrome #153
Conversation
I'm not sure about this one. |
As stated in #37, “when you sync with chrome it does not bring over any preferences form the extensions you have installed”, so you do not actually have everything in sync. This would do it. Another strong reason is, like @nZac stated, “this could be helpful if you don't want Google to own your data”. Syncing it this way is then superior in both configuration and privacy terms (and it also opens this option for people that use Chrome but do not have a Google account). I’d argue that users have no reason to sync Chrome with both |
Yes but enabling it by default would break a lot of configuration, e.g. everyone using a Google Account. |
And won't Chrome support syncing of extensions in the future ? Looks dumb from Google to not try to solve this problem. |
I’m not sure it would break existing configurations (it could, tough, so some testing is needed on this). I think you can actually sync preferences from extensions, but each extension must specify that (not sure, but I seem to remember reading something to that effect), which means it’s essentially useless, unless the developer does it, which is (as I see it) the exact use case for |
Updated to reflect the new way mackup is structured. |
Depends on #614 |
Doing some tests on this, this isn’t a good candidate for backup. If we’re too broad directories get huge (several GBs) and if we’re too narrow we won’t backup enough. |
nice, thanks for digging. |
In response to #37.