VDrift/vdrift — Issue #52: VDrift Content Tracker
Author: bigben87
Created: 2011-10-16 22:10:54+00:00
State: open

VDrift should have a system keeping track of the installed content to gather data about the actually installed content.
With this information a minimal data set with the most popular content could be created to minimize the initial download size while maintaining a positive first impression.

Content Tracker Server
--------------------------------

A central server should be setup to automate gathering the information.
The central server should store the name and the sha1 hash to keep track of different versions of content .
The central server should implement a web service accepting requests to store this information.
The central server should should store the data sets with timestamps to allow for trends to be calculated.

Client
--------

The VDrift Core should be extended to send the information to the server.
The VDrift Core should ask the user for permission to do this, once on the first start when this feature is available.
The VDrift Core should inform the user about what the usage data is needed for, where it is stored, how it is stored and who can access it.
The VDrift Core should save the choice in an configuration variable that is changeable, if the user changes his mind, later.

Proof of Concept
------------------------

A rudimentary proof of concept, which demonstrates the viability of hashing all content can be found under https://github.com/bigben87/VDriftContentTracker.