Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Note: You can take 10% off all Slashdot Deals with coupon code "slashdot10off." ×

Comment Re:Cancel or Allow? (Score 1) 233

How many people use their microphone that often? If they don't care about their own privacy over the inconvience of clicking a button then they probably deserve the privacy intrusion they're going to get.

How many people use their microphone that often?

I can think of users of Siri, users of OK Google, users of Cortana, users of voice-to-SMS, frequent users of VoIP, and people who use dictation because they have trouble using a standard keyboard. Someone who scans barcodes of products or scans personal checks from friends and family and payroll checks from employers too small for direct deposit might use the camera often.

I suggest a different privilege model for access to privacy-sensitive sensors:

  • Background access (while this origin or this app is open)
  • Foreground access (while this origin or this app is open and focused)
  • Temporary background access (revoked once all documents from this origin are unloaded, other than in navigation to another same-origin document, or all windows from this app are closed)
  • Temporary foreground access (default)
  • No access (do not ask user again)

Comment Re:What other ways? (Score 1) 233

Which side of the equation do the content creators care about the most? Would they rather provide the readers with value and treat them with respect, or suck up to those with the money?

If the choice is between trying to respect visiting readers while showing tasteful ads and trying to respect visiting readers while showing no ads, it depends on how much the authors want to keep a roof over their heads. The alternative (a paywall to cover authors' salaries and server costs) disrespects readers who are visiting, as paywalls lead to bounces, and bounces waste not only the reader's time but also server resources.

Comment Re:Will they also provide a way (Score 1) 166

There are a few lines you can add to the hosts file on your PC or your DNS proxy to block AdSense and DoubleClick networks. You don't have to go full APK unless you want to. Start with these two and see what else you can pull in from your browser's debugger.

Comment Cancel or Allow? (Score 1) 233

If access to your mic and camera are *actually* required (e.g. tech support, online chat etc.) you should have to authorise this access each time and the access should be granted for the current page only.

If the user has to re-allow the microphone, re-allow the camera, and re-allow location whenever the user navigates to a different part of a web application, with no way to "always allow" other than by applying a patch to the browser's source code and recompiling the entire browser from source, the user will likely consider it worse than Windows Vista UAC.

All Finagle Laws may be bypassed by learning the simple art of doing without thinking.