Privacybadger: Enhancement: Heuristic Data portablity

[smarkwell]

It seems that bootstrapping an installation is a potentially long process and essentially requires exposure to 3rd parties to determine how the data is used by each installation. While this is an excellent as far as data ownership and trust, for a person migrating between computers or even different browsers on the same computer, it would be nice to have some procedure to transfer heuristic data around that is friendly to users. Ideally in a way that would allow merging/syncing of the information.

[garrettr]

This should be pretty easy to implement, we can just export the relevant
data structures as JSON.

Additionally, if you use Firefox Sync/Firefox Accounts, this might be
handled automagically. I know it syncs add-ons, and I would expect it syncs
their storage too (I'll confirm with the FxA team).
On May 2, 2014 4:24 PM, "Scott Markwell" [email protected] wrote:

It seems that bootstrapping an installation is a potentially long process
and essentially requires exposure to 3rd parties to determine how the data
is used by each installation. While this is an excellent as far as data
ownership and trust, for a person migrating between computers or even
different browsers on the same computer, it would be nice to have some
procedure to transfer heuristic data around that is friendly to users.
Ideally in a way that would allow merging/syncing of the information.

—
Reply to this email directly or view it on GitHubhttps://github.com/EFForg/privacybadgerchrome/issues/121
.

[cooperq]

Chrome is also able to provide the functionality of syncing data across browsers but this could leak data to Google which a privacy conscious user may not wish to expose.
I think a better option might be adding the ability to export and import a json blob of your heuristic data.

[smarkwell]

I would argue that reasonable defaults would be the first step, but as far as the projects objectives go, is it against it's belief to allow that data into 3rd party hands? (Firefox Sync/Google Sync?) I guess that's a marketing of the project and clearly stating it's goals.

Is the risk of the data exposure or modification? Does that outweigh a consistent experience for users? Is there another sync technology that can be integrated too that meets the privacy goals?

[cooperq]

via @sequoia
"I filed a bug report but I realize it's probably really hard to reproduce reliably without knowing my specific badger settings. I'd like:

1. A way to easily export my settings for sharing between machines & filing bug reports
2. A way to transmit them privately to the Badger team for use reproducing bugs. E.g. a) export settings as .json, b) submit them to eff.org, c) receive ID/token I can paste into a bug report so devs can map my config to my bug report."

[cooperq]

Fixed by #982