Its fair not to trust Apple or any company, but Google and a lot of companies were scanning the cloud versions without the negative press Apple got. My understanding is Apple proposed scanning on-device because images were encrypted in the cloud. Uploading and have manual review process seems like a big ongoing cost.
Personally, I dont think Apple is doing anything with photos it stores in the cloud.
Like the first article says, technically they could, because they store the encryption key for user-convenience. Turning on Advanced Data Protection should take away their ability to decrypt photos. But there are a whole bunch of caveats if you're talking about all cloud their data and that has changed over the years.
> If you look at how Apple detects contraband imagery, they hash every image that gets uploaded into the photos app. Those hashes are transmitted to servers that compare them to hashes of known contraband.
You're spelling out a specific process in detail--which is the only reason I'm picking on details. Do you have anything documenting what you're describing?
From what I remember, Apple's system was proposed, but never shipped. They proposed hashing your photos locally and comparing them to a local database of known CSAM images. Only when there was was a match, they would transmit the photos for manual confirmation. This describes Apple's proposal [1].
I believe what did ship is an algorithm to detect novel nude imagery and gives some sort of warning for kids sending or receiving that data. None of that involves checks against Apple's server.
I do think other existing photo services will scan only photos you've uploaded to their cloud.
I'm happy to make corrections. To my knowledge, what you're describing hasn't been done so far.
I have no idea about Android, but my understanding is for wired CarPlay a GPS in the dash is optional and for wireless CarPlay its required. The thinking is you can use a larger, better placed antennae. If you're using wireless CarPlay you may have your phone hidden away.
Maybe. Real time and production often has special needs general purpose tools don't cover. A lot of delivery codecs focus on things like lossy compression and buffering. I know from video production and computer graphics, delivery codecs are miserable to work with for reasons such as: not allowing arbitrary channels (if you only need 1 channel or maybe you need 5 for an alpha and bump map), playing in reverse, cutting in on arbitrary frames, different compression on each channel (lossy rgb, but lossless alpha), etc. My understanding is that Bink is often used for realtime playback of multiple elements integrated with the 3d environment (triggered explosions, HUD elements, streaming textures) so it needs to be performant, handle many simultaneously, and integrated with the engine since you'd be applying transforms and LUTs.
It'll be nice if there are great, free, off the shelf codecs and tools, but at least right now almost every current AAA game seems to use Bink.
Apple got over having a "camera bump" on their phones years ago. On laptops they have way more options--the most straightforward would be to put a matching notch in the bottom-case for when it closes.
Finally higher quality build-in cameras are being included in iMacs. I hope very soon they start making their way into their laptops.
That's right. It is GNOME. KDE takes you right to recent logins and a login/password prompt (without a transition). I primarily work via VNC or ssh, but get questions constantly from new users. Wiggling the mouse is universally benign. ESC, Space, or even clicking can be "destructive" in the wrong context.
Oh, that's what that is supposed to be! The same thing is in CentOS. You literally click and drag the mouse upward to get the login screen. New users often think the computer is broken.
This article is a few years old, but has more of a plain-English, third party explanation: https://appleinsider.com/articles/20/01/21/what-apple-surren...
Its fair not to trust Apple or any company, but Google and a lot of companies were scanning the cloud versions without the negative press Apple got. My understanding is Apple proposed scanning on-device because images were encrypted in the cloud. Uploading and have manual review process seems like a big ongoing cost.
Personally, I dont think Apple is doing anything with photos it stores in the cloud.
Like the first article says, technically they could, because they store the encryption key for user-convenience. Turning on Advanced Data Protection should take away their ability to decrypt photos. But there are a whole bunch of caveats if you're talking about all cloud their data and that has changed over the years.