Would you share your PDC data?

Would you share your PDC data?

  • Yes

    Votes: 67 80.7%
  • No

    Votes: 16 19.3%

  • Total voters
    83

Please register or login

Welcome to ScubaBoard, the world's largest scuba diving community. Registration is not required to read the forums, but we encourage you to join. Joining has its benefits and enables you to participate in the discussions.

Benefits of registering include

  • Ability to post and comment on topics and discussions.
  • A Free photo gallery to share your dive photos with the world.
  • You can make this box go away

Joining is quick and easy. Log in or Register now!

Thanks for all the feedback! I haven't seen anything posted I hadn't anticipated, but the number of people indicating they would share their data is a bit higher than I expected.

For those concerned about privacy, I don't blame you. However, I think most concerns are misplaced. The data collected might show trends and provide some interesting data, but a third rate attorney could assure it was never used in a court. If, by some fluke of the justice system, it did make it into evidence, it would be easily discredited as a source of meaningful information.

If such an option existed, I would want the option for providing as much or as little info as I choose to provide. At minimum, the data uploaded would look like this:
That data is direct from my Sensus.
I would challenge anyone to use that info to give me a call, stop by my house, tell me who my employer is or tell me what my gross annual income is.

1. You assume that is the only data collected. However, any time you connect, you have session IDs, ip address exchanges, maybe cookies, and there is always a chance the end server was "0wn3d" and you might get a trojan dowloaded.

2. You can click whatever options for downloading that you wish, but what do you have that REALLY says what is downloaded? Is there a Privacy Act statement (Privacy Act of 1974, as amended) that states specifically what data they will have at any time, the uses of the data, with whom will they share it, and what their local protections are to keep a 3rd party from getting your data, or hijacking your session?

3. Do you have a sniffer trace that shows exactly what info was exchanged?

4. Do you run a NAT-capable firewall with antivirus, antispyware, and all in a default-deny configuration?

So sure are you?
 
Let's just take a look at your "dive data", Dave:

1,SU-04365,0029531894,2007,3,29,14,0,1,0,1243,296.31
1,SU-04365,0029531894,2007,3,29,14,0,1,10,1418,296.40
1,SU-04365,0029531894,2007,3,29,14,0,1,20,1553,296.44
1,SU-04365,0029531894,2007,3,29,14,0,1,30,1662,296.46
1,SU-04365,0029531894,2007,3,29,14,0,1,40,1762,296.49
1,SU-04365,0029531894,2007,3,29,14,0,1,50,1973,296.50
1,SU-04365,0029531894,2007,3,29,14,0,1,60,2092,296.53
1,SU-04365,0029531894,2007,3,29,14,0,1,70,2220,296.55
1,SU-04365,0029531894,2007,3,29,14,0,1,80,2321,296.56
1,SU-04365,0029531894,2007,3,29,14,0,1,90,2371,296.59
1,SU-04365,0029531894,2007,3,29,14,0,1,100,2420,296.60
1,SU-04365,0029531894,2007,3,29,14,0,1,110,2471,296.61
1,SU-04365,0029531894,2007,3,29,14,0,1,120,2510,296.63
1,SU-04365,0029531894,2007,3,29,14,0,1,130,2651,296.65
1,SU-04365,0029531894,2007,3,29,14,0,1,140,2622,296.66
1,SU-04365,0029531894,2007,3,29,14,0,1,150,2676,296.66
1,SU-04365,0029531894,2007,3,29,14,0,1,160,2748,296.68
1,SU-04365,0029531894,2007,3,29,14,0,1,170,2760,296.69
1,SU-04365,0029531894,2007,3,29,14,0,1,180,2721,296.69
1,SU-04365,0029531894,2007,3,29,14,0,1,190,2760,296.70
1,SU-04365,0029531894,2007,3,29,14,0,1,200,2837,296.70
1,SU-04365,0029531894,2007,3,29,14,0,1,210,2936,296.70
1,SU-04365,0029531894,2007,3,29,14,0,1,220,3147,296.71
1,SU-04365,0029531894,2007,3,29,14,0,1,230,3334,296.72
1,SU-04365,0029531894,2007,3,29,14,0,1,240,3339,296.73
1,SU-04365,0029531894,2007,3,29,14,0,1,250,3329,296.73

The first 27 of the 39 or 40 numbers repeat so that's not dive data, could be a serial number or processor ID or a date or all three

You have to go all the way to the 30th and 31st numbers to see change and they increase by 10 each time so that's not dive data either unless it's a 10 second interval - probably is

The numbers 31-35 also steadily increase as does the last 5 numbers which increase only by increments of .01, .02 or .03.

If that's dive data only three things that change are being reported - how useful could those three things be? Which do you think they are? Why would any researcher only use three parameters to make some judgement? I get a lot more data out of my computer than that. OR, maybe you're not getting all the data, you only think you are. Regardless, I'll bet that somewhere in the first set of 18 numbers, 1,SU-04365,0029531894, is your dive computer ID and it can be traced right to you.
 
Regardless, I'll bet that somewhere in the first set of 18 numbers, 1,SU-04365,0029531894, is your dive computer ID and it can be traced right to you.[/FONT]

Crap, you're absolutely correct... Still, the upload utility would be configured to strip any information you feel might be used to compromise your privacy.

As for the data conveyed, you have time, depth and temperature. Ascent rates, gas loading and profile can all be derived from the data provided in the sample.
 
Crap, you're absolutely correct... Still, the upload utility would be configured to strip any information you feel might be used to compromise your privacy.

As for the data conveyed, you have time, depth and temperature. Ascent rates, gas loading and profile can all be derived from the data provided in the sample.

Would be, could be, should be.
You've just made our case why it shouldn't be!
Most people wouldn't have the knowledge or insight to check the data to make sure. You do and still goofed and posted your PDC SN# in the open on SB.
:no::rofl3::popcorn:
 
Would be, could be, should be.
You've just made our case why it shouldn't be!
Most people wouldn't have the knowledge or insight to check the data to make sure. You do and still goofed and posted your PDC SN# in the open on SB.
:no::rofl3::popcorn:

YES! Finally!!!! I've been waiting to get my hands on the serial number of another person's dive computer! Now, let the evil plans commence :homealone:
 
Let's just take a look at your "dive data", Dave:


1,SU-04365,0029531894,2007,3,29,14,0,1,0,1243,296.31


1,SU-04365,0029531894,2007,3,29,14,0,1,10,1418,296.40


1,SU-04365,0029531894,2007,3,29,14,0,1,20,1553,296.44


1,SU-04365,0029531894,2007,3,29,14,0,1,30,1662,296.46


1,SU-04365,0029531894,2007,3,29,14,0,1,40,1762,296.49


1,SU-04365,0029531894,2007,3,29,14,0,1,50,1973,296.50

This sounds like fun: let me try:
1 - reset line (new record)
SU brand name
04365 - model number
0029531894 - serial number
2007, 3, 29 - date of the dive in yyyy, m, dd
14, 0,1, 30, 40, 50 . . . 1401 hours (that's 2:01p), and counting seconds 30, 40, 50.
then the real data is in the 1973,296.50 . . . which may link to another table in the database the PDC holds.

How'd I do?
 
UsryTregre:
Really? I did my skiing in Austria, Germany, France, Switzerland, and Italy -- thought that was enough of Europe to say "Europe". Going off-piest (piezt? I forget) was perfectly okay . . . I was just warned that any rescue off the groomed areas would cost me in the thousands, while rescue on the piested (sp?) areas were covered by my ADAC insurance, no prob. I had a lot of friends that loved fresh powder, and I would on occasion join them. But by doing so, I was assuming all responsibility for my decision.
There is a lot more than 5 countries in europe last I checked..
 
Close. SU is the model, 04365 the serial. I think the longer number is the dive ID. I'll have to check the log.
This sounds like fun: let me try:
1 - reset line (new record)
SU brand name
04365 - model number
0029531894 - serial number
2007, 3, 29 - date of the dive in yyyy, m, dd
14, 0,1, 30, 40, 50 . . . 1401 hours (that's 2:01p), and counting seconds 30, 40, 50.
then the real data is in the 1973,296.50 . . . which may link to another table in the database the PDC holds.

How'd I do?
 
Close. SU is the model, 04365 the serial. I think the longer number is the dive ID. I'll have to check the log.

That's it, keep feeding me the info. Little by little, I am going to get you! When you least expect it, WHAM! Before you know it, you are going to find yourself in court defending your decision to only do a 2 mnute and 55 second safety stop from 17 feet instead of the full 3 from 15! Your mine, sucker!
 
Crap, you're absolutely correct... Still, the upload utility would be configured to strip any information you feel might be used to compromise your privacy.

As for the data conveyed, you have time, depth and temperature. Ascent rates, gas loading and profile can all be derived from the data provided in the sample.

That's my point, again, Dave....these values are going to be used to "derive" other data. If I were a lawyer I could "derive" you right into a bad outcome, guaranteed. If I wanted to make any sort of point I could manipulate the derived data and make my point. You and I are not the same physically and if we dove the exact same profile with the exact same computer producing two sets of the exact same data the derived data would not accurately describe what is actually going on physically with either of us. There isn't enough data. So unless the data set is full enough and distinct enough and accurate enough it really doesn't tell you much. But you sure can have fun playing around with it! And someone will know it's YOU, Dave. I rest my case (damn, starting to sound like a lawyer :D).
 

Back
Top Bottom