Skip to content
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

Closed
wants to merge 1 commit into from
Closed

added support for Google Chrome #153

wants to merge 1 commit into from

Conversation

vitorgalvao
Copy link
Contributor

In response to #37.

@lra
Copy link
Owner

lra commented Jan 12, 2014

I'm not sure about this one.
I use Google Chrome and everything is already in sync by using a Google Account.
I'm scared that it would conflict with the internal syncing system of GChrome.

@vitorgalvao
Copy link
Contributor Author

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 mackup and Google’s system, and mackup does allow you control what is synced and what is not. Maybe this could be added as “do not sync unless specifically told to”, like (arguably) ssh should be.

@lra
Copy link
Owner

lra commented Jan 12, 2014

Yes but enabling it by default would break a lot of configuration, e.g. everyone using a Google Account.
There is still no clear way to not enable every app sync by default.

@lra
Copy link
Owner

lra commented Jan 12, 2014

And won't Chrome support syncing of extensions in the future ? Looks dumb from Google to not try to solve this problem.

@vitorgalvao
Copy link
Contributor Author

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 mackup (after all, if every developer provided a syncing option, you wouldn’t have needed to build this tool in the first place).

@vitorgalvao
Copy link
Contributor Author

Updated to reflect the new way mackup is structured.

@lra
Copy link
Owner

lra commented Aug 9, 2015

Depends on #614

@lra lra added the Blocked label Aug 10, 2015
@lra lra mentioned this pull request Aug 10, 2015
@vitorgalvao
Copy link
Contributor Author

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.

@lra
Copy link
Owner

lra commented Sep 30, 2015

nice, thanks for digging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants