send list of installed Libraries, Modes, Tools, and Examples when update checking #3365

Closed
REAS opened this Issue Jun 8, 2015 · 10 comments

Comments

Projects
None yet
4 participants
@REAS
Member

REAS commented Jun 8, 2015

Should we add something to include the library/mode/tool list (and versions) when checking for updates? We’ve discussed it before, but haven't made a hard decision.

@benfry benfry changed the title from Library, Modes, Tools, and Example Stats to send list of installed Libraries, Modes, Tools, and Examples when update checking Jun 8, 2015

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Jun 8, 2015

Member

I think it's a good idea and should be harmless. Users can turn it off by unsetting the "don't check for updates" preference. Which is also noted in the FAQ.

Member

benfry commented Jun 8, 2015

I think it's a good idea and should be harmless. Users can turn it off by unsetting the "don't check for updates" preference. Which is also noted in the FAQ.

@alignedleft

This comment has been minimized.

Show comment
Hide comment
@alignedleft

alignedleft Jun 11, 2015

Member

@REAS to clarify: We currently just check for updates to the IDE. Are you proposing also auto-checking for updates to all installed contributions?

I think this would be great, but it would require auto-downloading contribs.txt every time the IDE is opened (or once a week, or once per whatever time period is set). Is @benfry OK with that additional hit to the server? This would also involve more complex logic under the hood than the current IDE version check.

Member

alignedleft commented Jun 11, 2015

@REAS to clarify: We currently just check for updates to the IDE. Are you proposing also auto-checking for updates to all installed contributions?

I think this would be great, but it would require auto-downloading contribs.txt every time the IDE is opened (or once a week, or once per whatever time period is set). Is @benfry OK with that additional hit to the server? This would also involve more complex logic under the hood than the current IDE version check.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Jun 11, 2015

Member

Yeah, we're already doing that, it's the only way to keep the contribs up to date.

The thing to be implemented is to send a list of the user's currently installed modes/libraries/tools (and versions?) so that we understand what people are using and where to focus our efforts on getting things updated/fixed/improved.

Member

benfry commented Jun 11, 2015

Yeah, we're already doing that, it's the only way to keep the contribs up to date.

The thing to be implemented is to send a list of the user's currently installed modes/libraries/tools (and versions?) so that we understand what people are using and where to focus our efforts on getting things updated/fixed/improved.

@eric-brechemier

This comment has been minimized.

Show comment
Hide comment
@eric-brechemier

eric-brechemier Jun 11, 2015

@benfry There should be a different checkbox for the submission of user's config, separate from the permission to check for updates.

For example, Firefox has currently two checkboxes in Preferences > Advanced > Data Choices, each associated with a link to 'Learn More':

@benfry There should be a different checkbox for the submission of user's config, separate from the permission to check for updates.

For example, Firefox has currently two checkboxes in Preferences > Advanced > Data Choices, each associated with a link to 'Learn More':

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Jun 11, 2015

Member

Firefox also has 10-100x as many preferences as Processing. It's not like this is sharing personal information, and if people want to shut it off, they can.

Member

benfry commented Jun 11, 2015

Firefox also has 10-100x as many preferences as Processing. It's not like this is sharing personal information, and if people want to shut it off, they can.

@eric-brechemier

This comment has been minimized.

Show comment
Hide comment
@eric-brechemier

eric-brechemier Jun 11, 2015

@benfry I personally feel uncomfortable with this change: while the FAQ states that the check for updates sends a uniquely identifying number, which is arguably a limited breach of privacy when used in isolation, sharing the list of Libraries, Modes, Tools, and Examples that I installed over time could be much more revealing.

@benfry I personally feel uncomfortable with this change: while the FAQ states that the check for updates sends a uniquely identifying number, which is arguably a limited breach of privacy when used in isolation, sharing the list of Libraries, Modes, Tools, and Examples that I installed over time could be much more revealing.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Jun 11, 2015

Member

The feature doesn't exist yet, so the FAQ hasn't been updated, nor has the phrasing of the text used in Preferences.

Member

benfry commented Jun 11, 2015

The feature doesn't exist yet, so the FAQ hasn't been updated, nor has the phrasing of the text used in Preferences.

@eric-brechemier

This comment has been minimized.

Show comment
Hide comment
@eric-brechemier

eric-brechemier Jun 11, 2015

@benfry I am aware of that :) I do not expect the FAQ to describe a future implementation. While I feel OK with the current behavior as it is described in the FAQ, I am wary of the extension of the data collection in the name of "checking for updates".

@benfry I am aware of that :) I do not expect the FAQ to describe a future implementation. While I feel OK with the current behavior as it is described in the FAQ, I am wary of the extension of the data collection in the name of "checking for updates".

@REAS

This comment has been minimized.

Show comment
Hide comment
@REAS

REAS Jun 11, 2015

Member

We feel that this information is important for the development of the software, so I think people who are uncomfortable with it can and should flip the switch in the preferences.

Member

REAS commented Jun 11, 2015

We feel that this information is important for the development of the software, so I think people who are uncomfortable with it can and should flip the switch in the preferences.

@alignedleft

This comment has been minimized.

Show comment
Hide comment
@alignedleft

alignedleft Jun 11, 2015

Member

On the web side, we probably need a PHP script or other way to receive and log the IDs of the installed contributions. Does that sound correct, @benfry? We could even consolidate things, so instead of one check for IDE version and one for all contributions, all values are returned from a single call to the server.

Member

alignedleft commented Jun 11, 2015

On the web side, we probably need a PHP script or other way to receive and log the IDs of the installed contributions. Does that sound correct, @benfry? We could even consolidate things, so instead of one check for IDE version and one for all contributions, all values are returned from a single call to the server.

@benfry benfry added the high label Jun 15, 2015

@benfry benfry modified the milestone: GSOC 14 - Joel/Florian Jun 15, 2015

@benfry benfry removed the high label Jun 15, 2015

@benfry benfry added this to the 3.0 beta 1 milestone Jun 15, 2015

@benfry benfry closed this in 3a928f1 Jun 23, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment