3 ms·

>Apple doesn't cheat me on my privacy when I buy a machine. Except that siri thing

by delfinom 7y ago

Austin_Conlon 7y ago
Could you elaborate? “Hey Siri” is opt-in when you set up a Mac.
- Wowfunhappy 7y ago
  GP is referring to the fact that Apple contractors were manually reviewing Siri recordings, which frequently included private conversations in which Siri activated erroneously. "Hey Siri" may be opt in, but you're encouraged to enable it when you set up a new device, and someone who turns it on isn't necessarily okay with their private conversations being reviewed. Buying a computer in the first place is technically "opt-in" too.
rubbingalcohol 7y ago
The installer itself lets you choose to enable or disable Siri. Like it's one of the first choices you make when you first set up the machine.
- Broken_Hippo 7y ago
  As someone else pointed out: That isn't the issue. It was because they lied about your privacy when you opted in. Some folks, would they have known what they know now, wouldn't have opted in.
  - emsy 7y ago
    Still important. Try to get rid of Cortana for instance. MS is forcing that crap down your throat.
    - wtallis 7y ago
      At the moment, if you set Windows 10 to not send every keystroke to Bing when you're searching for a start menu shortcut, the search process locks up and consumes an entire CPU core. Microsoft isn't serious about the privacy options they pretend to offer.
      - NullPrefix 7y ago
        Wait what? This cannot be serious.
        wtallis 7y ago
        Apparently Microsoft did get a fix out earlier this week; I'd been avoiding my Windows machines waiting for this. The patch that introduced the bug: https://support.microsoft.com/en-us/help/4512941/windows-10-update-kb4512941 https://support.microsoft.com/en-us/help/4512941/windows-10-... The patch that fixed the bug: https://support.microsoft.com/en-us/help/4515384/windows-10-update-kb4515384 https://support.microsoft.com/en-us/help/4515384/windows-10-... Description and workaround: https://www.reddit.com/r/Windows10/comments/cxmot9/windows_10_1903_update_18362329_causes_high_cpu/ https://www.reddit.com/r/Windows10/comments/cxmot9/windows_1... It's still clear that Microsoft's QA procedures focus too highly on testing the default configurations rather than the sane configurations.

>Apple doesn't cheat me on my privacy when I buy a machine. Except that siri thing

Austin_Conlon 7y ago

Could you elaborate? “Hey Siri” is opt-in when you set up a Mac.

Wowfunhappy 7y ago
GP is referring to the fact that Apple contractors were manually reviewing Siri recordings, which frequently included private conversations in which Siri activated erroneously. "Hey Siri" may be opt in, but you're encouraged to enable it when you set up a new device, and someone who turns it on isn't necessarily okay with their private conversations being reviewed. Buying a computer in the first place is technically "opt-in" too.

rubbingalcohol 7y ago

The installer itself lets you choose to enable or disable Siri. Like it's one of the first choices you make when you first set up the machine.

Broken_Hippo 7y ago
As someone else pointed out: That isn't the issue. It was because they lied about your privacy when you opted in. Some folks, would they have known what they know now, wouldn't have opted in.
- emsy 7y ago
  Still important. Try to get rid of Cortana for instance. MS is forcing that crap down your throat.
  - wtallis 7y ago
    At the moment, if you set Windows 10 to not send every keystroke to Bing when you're searching for a start menu shortcut, the search process locks up and consumes an entire CPU core. Microsoft isn't serious about the privacy options they pretend to offer.
    - NullPrefix 7y ago
      Wait what? This cannot be serious.
      - wtallis 7y ago
        Apparently Microsoft did get a fix out earlier this week; I'd been avoiding my Windows machines waiting for this. The patch that introduced the bug: https://support.microsoft.com/en-us/help/4512941/windows-10-update-kb4512941 https://support.microsoft.com/en-us/help/4512941/windows-10-... The patch that fixed the bug: https://support.microsoft.com/en-us/help/4515384/windows-10-update-kb4515384 https://support.microsoft.com/en-us/help/4515384/windows-10-... Description and workaround: https://www.reddit.com/r/Windows10/comments/cxmot9/windows_10_1903_update_18362329_causes_high_cpu/ https://www.reddit.com/r/Windows10/comments/cxmot9/windows_1... It's still clear that Microsoft's QA procedures focus too highly on testing the default configurations rather than the sane configurations.