Option to set up the period time for checking for available updates (including usage statistics)

[DrSooom]

Path:

NVDA menu » Preferences » Settings... » General

Actual behaviour:

As the new function "Allow the NVDA project to gather NVDA usage statistics" is binding with the update check, it could lead on some specific cases to an privacy issue because it might be possible to find out based on the collected data individual users. Note that in some countries the amount of NVDA users are very rare. And if they are moving with their NVDA copy into another country you might be able to see this in the collected data if the update check period is set up to shortly. And currently I as an end user can't see how often NVDA checks for updates. It isn't mentioned in the manual (en/userGuide.html).

Expected behaviour:

Replace the checkbox "Automatically check for updates to NVDA" to a combobox with the same title and the following values: Never, On NVDA start up, Every day, Every third day, Every week, Every second week and Every month.

System configuration:

NVDA version:

NVDA alpha-15554,66186bfb

[josephsl]

Hi, ah, I can offer a pull request regarding this within the next 24 hours (asking an add-on to volunteer its code and idea), but let us hear some rationale from many sides before committing to it. Also, there is a really crucial design flaw with the proposed solution: update check intervals are not static (in terms of possible options). Thanks. From: Daniel Mayr <notifications@github.com> Sent: Wednesday, July 18, 2018 12:12 PM To: nvaccess/nvda <nvda@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [nvaccess/nvda] Option to set up the period time for checking for available updates (including usage statistics) (#8514) Path: NVDA menu » Preferences » Settings... » General Actual behaviour: As the new function "Allow the NVDA project to gather NVDA usage statistics" is binding with the update check, it could lead on some specific cases to an privacy issue because it might be possible to find out based on the collected data individual users. Note that in some countries the amount of NVDA users are very rare. And if they are moving with their NVDA copy into another country you might be able to see this in the collected data if the update check period is set up to shortly. And currently I as an end user can't see how often NVDA checks for updates. It isn't mentioned in the manual (en/userGuide.html). Expected behaviour: Replace the checkbox "Automatically check for updates to NVDA" to a combobox with the same title and the following values: Never, On NVDA start up, Every day, Every third day, Every week, Every second week and Every month. System configuration: NVDA version: NVDA alpha-15554,66186bfb — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#8514> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkAe4kzvCxQR-FGFnsITTYhadkWB6ks5uH4iDgaJpZM4VVL-i> .

[DrSooom]

I found bug #2353, but as you also combined sending additional metadata during the update check, this ticket here shouldn't be closed.

Furthermore I suggest to set the update period to every or every second week by default. those who are using alpha and beta build should have enough knowledge what is the best period for them. And if users really installs RCs on their productive systems, it is still enough to notify them weekly about the availability of new RCs or stable builds.

And I'm also asking me why you need 24 hour updated statistics. Collecting stats weekly should be provide similar data as daily once, but it enhance the privacy a little bit as a timestamp could also be stored with the rest of the sending metadata during the update check. this is also a very important point which I found no info about this in the User Guide. Are now those metadata stored with a timestamp or not? I can't answer this because of too less information.

[Adriani90]

@josephsl you mentioned you could provide a pull request on this. Do you still have your work on this? Or is it obsolete?