Send device info to a server
We can collect a few pieces of data from the mtp-detect program:
* device manufacturer and model
* libmtp version
*device friendly name
This would be run once only. During a new install/updated version install.
The data will be sent to a server where it is collated, so we can give users an accurate list of which devices work.
A "Not Working?" button:
The user should be able to mark the device as non-operational with the software, sending these details (optional email and an mtp-file dump) to a server so we can take a final look at it before marking it as officially non operational.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Low
- Drafter:
- Daniel Woodhouse
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- Accepted for 1.0
- Implementation:
-
Not started
- Milestone target:
-
1.0a
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
- Yeah, It may be very usable. As you said, I can to the client side. We need to look some possibilities how we do this, encrypted connection or not and etc. Series goal set to 1.0, at least to it -- Saku Laukkanen
- I'll work on the server API this weekend and send you a draft as soon as possible. My current idea is to run the server on google app engine, which uses a bigtable database. The first time run wizard is a good idea, so we will implement that. It should also run for current users as well, it would be a good way to get an idea of how many users we have.
I don't think we need to worry about encrypted connections, as we wont be sending any private data, except perhaps an email address if the user was having problems.
I have added a wiki it's available at http://
- Ok. The first run wizard should add that "first run wizard has runned for this account" to user's database file. Then it would run to current users after update anyway. Should be quite easy to do, no problem! --Saku Laukkanen
