4 ms·

The APIs powering this are in the process of being heavily restricted or removed altogether -- if you think games like this should exist, you should voice your

The APIs powering this are in the process of being heavily restricted or removed altogether -- if you think games like this should exist, you should voice your concern here: https://github.com/w3c/deviceorientation/issues/57 https://github.com/w3c/deviceorientation/issues/57.

snazz 8y ago
It looks to me that they’re just adding a permission for gyro access instead of turning it off altogether. Did I misread it?
- KenanSulayman 8y ago
  https://github.com/w3c/deviceorientation/issues/57#issuecomment-451985213 https://github.com/w3c/deviceorientation/issues/57#issuecomm...
  - teraflop 8y ago
    That comment does not say the APIs are in the process of being removed. And asking people to comment on the issue to say that they shouldn't be removed would not be helping the discussion, because that point has already been made in the thread by at least three people that I count.
    - beatgammit 8y ago
      Since it's GitHub, just add a thumbs up or whatever to the comment in question, don't just add me too comments. That's the way I've seen voting work best in GitHub.
zchrykng 8y ago
If the app doesn't want to ask permission before gathering my data, they can pound sand.
- doodpants 8y ago
  It seems to me that gyroscope data is merely input, rather than personal data. In other words, I'm not sure asking permission before accessing gyroscope data makes any more sense than asking permission before accepting touch screen input. Or for desktop applications, asking permission before accepting keyboard/mouse input.
  - saagarjha 8y ago
    Collecting gyroscope data is quite passive, though. It's easy to forget that an app/website has access to this.
    - beatgammit 8y ago
      And it's also more concerning from a privacy perspective since it's the position of something outside of the app (the phone) instead of inside of the app. Mouse coordinates work this way (only get cursor updates within your browser tab content area), so it makes sense to require permission from the user before accessing it.

snazz 8y ago

It looks to me that they’re just adding a permission for gyro access instead of turning it off altogether. Did I misread it?

KenanSulayman 8y ago
https://github.com/w3c/deviceorientation/issues/57#issuecomment-451985213 https://github.com/w3c/deviceorientation/issues/57#issuecomm...
- teraflop 8y ago
  That comment does not say the APIs are in the process of being removed. And asking people to comment on the issue to say that they shouldn't be removed would not be helping the discussion, because that point has already been made in the thread by at least three people that I count.
  - beatgammit 8y ago
    Since it's GitHub, just add a thumbs up or whatever to the comment in question, don't just add me too comments. That's the way I've seen voting work best in GitHub.

zchrykng 8y ago

If the app doesn't want to ask permission before gathering my data, they can pound sand.

doodpants 8y ago
It seems to me that gyroscope data is merely input, rather than personal data. In other words, I'm not sure asking permission before accessing gyroscope data makes any more sense than asking permission before accepting touch screen input. Or for desktop applications, asking permission before accepting keyboard/mouse input.
- saagarjha 8y ago
  Collecting gyroscope data is quite passive, though. It's easy to forget that an app/website has access to this.
  - beatgammit 8y ago
    And it's also more concerning from a privacy perspective since it's the position of something outside of the app (the phone) instead of inside of the app. Mouse coordinates work this way (only get cursor updates within your browser tab content area), so it makes sense to require permission from the user before accessing it.