You can generate a new ID whenever you want, so it's useless for actually tracking anyone even if it were possible.
Making Dolphin More Productive - Optional Usage Statistics Reporting
|
06-21-2016, 05:44 PM
(06-21-2016, 08:18 AM)Skywolf Wrote: So what information does this collect exactly? From the link to Analytics.cpp can I only see it collecting information about hardware/OS and the settings used. I assume it does more because that information on itself isn't all that usefull when looking for issues. It doesn't do that much more right now, other than checking which games are played. More advanced things have to wait until after the release of 5.0 so that the release doesn't get delayed too much. You're right in that the data that currently is collected is hard to use for solving issues. (06-21-2016, 08:18 AM)Skywolf Wrote: Like how much is sent when something does go wrong? Nothing, as far as I know. (06-21-2016, 08:18 AM)Skywolf Wrote: Also not sure how I feel about Dolphin making an unique ID for each user. Feels to me like unnecessary information that could be used to indentify someone. The point of it is to be able to distinguish between one user running Dolphin many times and several users running Dolphin once each. How well can we identify individual users with this? Not well at all, actually. We can know that one user has a so-and-so CPU and so-and-so GPU, but we can't connect that to things like which games are played. When reporting data for a game, a unique ID is used that we can't match to IDs sent for other games or the ID sent at boot, as described here: https://github.com/dolphin-emu/dolphin/p...-226973589 06-22-2016, 12:02 AM
(06-21-2016, 03:42 PM)JMC47 Wrote: You can generate a new ID whenever you want, so it's useless for actually tracking anyone even if it were possible.That is like saying Tracing Cookies are OK because the user can remove them. (06-21-2016, 05:44 PM)JosJuice Wrote: It doesn't do that much more right now, other than checking which games are played. More advanced things have to wait until after the release of 5.0 so that the release doesn't get delayed too much. You're right in that the data that currently is collected is hard to use for solving issues.If there are plans for having more information sent in the future then I would like Dolphin to inform the users about this. Preferably with a small list in human readable text (not just a link to source code) so people know what information will be sent when they start a new build for the first time. (06-21-2016, 05:44 PM)JosJuice Wrote: The point of it is to be able to distinguish between one user running Dolphin many times and several users running Dolphin once each. How well can we identify individual users with this? Not well at all, actually. We can know that one user has a so-and-so CPU and so-and-so GPU, but we can't connect that to things like which games are played. When reporting data for a game, a unique ID is used that we can't match to IDs sent for other games or the ID sent at boot, as described here: https://github.com/dolphin-emu/dolphin/p...-226973589Doesn't it also get to know from which IP address the data came from? And can't that be used to connect the IDs? Although I guess that can be said for any data being sent. Still would defeat the purpose of this ID system. Is there somewhere a Privacy Policy/Statement somewhere for this though? That could probably answer alot of questions provided it is written in human english (not lawyer jargon). Sorry if I sound like a paranoid jerk or something. That is not my intention but in this age of privacy invasion you can't play it save enough. Which is a shame because I really would like to help out Dolphin in any way possible. Just not at the price of my soul privacy. 06-22-2016, 06:33 AM
I plan to run my main gaming rig offline so you won't be able to gather performance data. However I'd still like to contribute. Any suggestions.
06-22-2016, 09:50 AM
Some of my HTC Vive users might go crazy over this. LOL. But I think it's a good idea.
Quote:[color=#000000]We can know that one user has a so-and-so CPU and so-and-so GPU, but we can't connect that to things like which games are played[/color] That seems like a bad idea. If people are having issues with a game, we're going to want to know what hardware they're running it on. I think our tinfoil hat is a little too tight. Being concerned about privacy over this is silly. The worst case scenario would be "You said you were playing Mario Kart, but you're actually playing the shovelware game Fantasy Aquarium World! You thought you could hide it, but our elite hacking skills caught you!" And that's still extremely unlikely. They can't even be caught doing anything illegal (although maybe it would be better if they could be caught) because dumping the game yourself from your Wii produces identical results to downloading it, and besides there wouldn't be any way of knowing whether people who did download a game had already bought and paid for it (but couldn't work out how to install Homebrew channel on their Wii and dump it), or not. As long as it's not tied to your IP address, I can't see any possible way the data could be used maliciously, or for anything other than developing a better emulator. 06-22-2016, 04:59 PM
(06-22-2016, 09:50 AM)CarlKenner Wrote: That seems like a bad idea. If people are having issues with a game, we're going to want to know what hardware they're running it on. I think our tinfoil hat is a little too tight. The CPU and GPU information is also sent when starting a game, but then it uses a per-game ID. So while we can get information about what's being used for one game, we can't reliably connect that to whether other games were played by the same user. (Also, correction to what I said earlier: The GPU information is not actually sent at boot, only when starting a game.) |
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)