Arctucas wrote
jv16 wrote
Arctucas wrote
So far, so good.
One thing that irks me; PowerTools 'phoning home'.
It immediately tries to make several internet connection upon install, and the "Automatically check for product updates" is set by default.
That's because we don't want people to use old versions of the app. Before having the automatic check for product updates feature, we would get feedback and bug reports of versions which were months or even years old. I'm sure you can understand that it's very frustrating to realize people are using very old program versions without knowing there are updated versions available.
The details of what data is being sent during these connections is detailed in the program's License Agreement (a copy of which is stored at \jv16 PowerTools\Help\License Agreement.txt).
Plus, you can disable the automatic product updates checks if you don't wish to use that feature.
With all these points, I would say jv16 PowerTools is one of the more privacy friendly apps out there.
All fair points.
Except, my belief is that it should be the option and responsibility of the end user.
If we leave this to the end users, then we are back at square one, having people using many years old versions of the program. Which is why we have the option for the app to check for updates, and that you can disable that if you don't wish to use that. Unlike in many other apps, where you cannot disable such functionality at all. So, again, I would argue that jv16 PowerTools is much more user friendly and privacy friendly than most other apps out there.
Arctucas wrote
Perhaps during installation, a pop-up appears (before PowerTools initiates internet connection attempt) that states something to the effect of "Thank you for choosing to install PowerTools. Would you like to allow the application to connect to the internet to check for the latest version?"
Also, another pop-up could state "PowerTools is able to check automatically for updates. Would you like to enable this option?"
I don't think our installation system (NSIS) supports such functionality, but what we could do is add this as an option to the installer as a checkbox that users can disable if they so wish. I think that could work.