ooni-probe-cli/cmd/ooniprobe/internal/ooni/default-config.json

{
  "_version": 1,
  "_informed_consent": false,
  "sharing": {
    "upload_results": true
  },
  "nettests": {
    "websites_max_runtime": 0
  },
  "advanced": {}
}
Add functions to handling migration from legacy OONI Probe 2018-02-12 11:18:14 +01:00			`{`
Remove all settings which are not implemented (#73) * Remove all settings which are not implemented * Add support for migrating config files from version 0 -> 1 Add basic unittests for the config file migration * Update the config file used by travis * Fix typos in console log messages * Improve the comment * Fix type of limit * Set informed consent to true in the travis config 2019-11-14 17:58:31 +01:00			`"_version": 1,`
Consolidate config related functionality into the config package 2018-06-22 10:29:47 +02:00			`"_informed_consent": false,`
Add functions to handling migration from legacy OONI Probe 2018-02-12 11:18:14 +01:00			`"sharing": {`
Fix default config and version 2018-07-14 16:58:08 +02:00			`"upload_results": true`
Add functions to handling migration from legacy OONI Probe 2018-02-12 11:18:14 +01:00			`},`
Remove all settings which are not implemented (#73) * Remove all settings which are not implemented * Add support for migrating config files from version 0 -> 1 Add basic unittests for the config file migration * Update the config file used by travis * Fix typos in console log messages * Improve the comment * Fix type of limit * Set informed consent to true in the travis config 2019-11-14 17:58:31 +01:00			`"nettests": {`
feat(ooniprobe): introduce websites_max_runtime (#273) We cannot control anymore the maximum number of URLs using the API because now we are using check-in, that has no such limit. We could theoretically clamp the number of URLs to measure after the call to check-in, and still honour the setting. Yet, the right thing to do seems to introduce a max runtime variable because that is what desktop and mobile do. Thus, introduce code that warns the user about the change in the settings, should they have set the URL limit to nonzero. We are going to do a best effort conversion from the URL limit to the maximum runtime for the rest of 2021. Since then, we will silently ignore the URL limit. This work is part of https://github.com/ooni/probe/issues/1299. 2021-03-30 11:16:12 +02:00			`"websites_max_runtime": 0`
Add functions to handling migration from legacy OONI Probe 2018-02-12 11:18:14 +01:00			`},`
cleanup(ooniprobe): remove unused send_crash_report option (#578) Closes https://github.com/ooni/probe/issues/1766 2021-11-05 13:26:08 +01:00			`"advanced": {}`
Add functions to handling migration from legacy OONI Probe 2018-02-12 11:18:14 +01:00			`}`