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.

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.

[1] https://www.hackerfactor.com/blog/index.php?/archives/929-On...

I mostly work in a different domain than webdev, but feel strongly about trying to decouple base technologies of your OS and your application as much as possible.

It's one thing if you are using a Linux image and choose to grab their Python package and other if their boot system is built around the specific version of Python that ships with the OS. The goal being if you later need to update Python or the OS they're not tethered together.

I'm very confused by this. From what I've seen it's been getting a lot better (since transitioning from CRTs). At least for television, frame-rate matching is becoming more of a thing. Higher frame rates really help. Calling everything fps for simplicity; 120 divides evenly by 24, 30, and 60. Lower values wont match and cause issues.

Similarly, (maybe back in the 90s?) projectors in theaters would double-expose each frame to reduce the flicker in between frames. With digital, they no longer have to advance the film between frames.

> smooth motion like credits at certain speeds are extremely uncomfortable to look at at these frame rates.

I think scrolling credits are the most difficult use case: white on black with hard text and no blur. DLP projectors (common 10+ years ago) drive me nuts displaying R G and B separately.

Outside of credits, cinematographers and other filmmakers do think about these things. I remember hearing a cinematographer talk about working on space documentaries in Imax. If you panned too quickly, the white spaceship over a black star field could jump multiple feet each frame. Sure films shot today are optimized for the theater, but the technology gap between theater and home is nowhere near as crazy as CRT vs acetate.

> Frame size is different from the other parameters, as it is solely a physical practicality.

I'm still struggling to see how its that different. Widescreen meant a lower effective resolution (it didn't have to--it started with Cinerama and Cinemascope), but was adopted for cost and aesthetic reasons.

> If some technology somewhere else in the stack causes a change…and soon all content aligns on the format, and the majority of home TV sets will be shaped to fit the majority content it can receive.

And the industry and audiences are really attached to 24fps. Like you say, home televisions adopted film's aspect ratio and I've also seen them adopt much better support for 24fps.

As kind of an aside, I wonder if the motion blur is what people are attached to more than the actual frame rate. I assume you're talking about frame rates higher than 30? Sure, we have faster films and brighter lights, but exposure time is really short. I saw the Hobbit in theaters in both high frame rate and 24fps and the 24fps one looked weird to me, too--I meant to look it up, but I assume they just dropped frames making the blur odd.

How? Disclosure should already be legally required--class-actions and lawsuits should already be a thing. The Have I Been Pwned data sets aren't volunteered by these companies. It's a catalog of leaked data.

The class-action response of "identity monitoring" is nonsense. More companies, if they can't afford to or don't want secure data, shouldn't collect it or should aggressively purge it. User data should be a liability.

All of it (lens flares, motion blur, film grain, DoF, tone mapping, and exposure, frame rate) are artistic choices constrained by the equipment we have to collect and present it. I think they'll always follow trends. In my entire career following film, photography, computer graphics, and game dev the only time I've heard anyone talk about how we experience any of those things is when people say humans see roughly equivalent of a 50mm lens (on 35mm film).

Just look at the trend of frame size. Film was roughly 4:3, television copied it. Film started matting/cropping the frame. It got crazy with super wide-screen to where some films used 3 projectors side-by-side and most settled on 16:9. Then television copied it. Widescreen is still seen as more "filmic." I remember being surprised working on a feature that switched to Cinemascope's aspect ratio and seeing that was only 850 pixels tall--a full frame would be about twice that.

To me, high frame rate was always just another style. My only beef was with motion-smoothing muddying up footage shot at different frame rates.

It may not be obvious, but film has a visual language. If you look at early film, it wasn't obvious if you cut to something that the audience would understand what was going on. Panning from one object to another implies a connection. It's built on the visual language of still photography (things like rule of thirds, using contrast or color to direct your eye, etc). All directing your eye.

Stereo film has its own limitations that were still being explored. In a regular film, you would do a rack focus to connect something in the foreground to the background. In stereo, when there's a rack focus people don't follow the camera the same way. In regular film, you could show someone's back in the foreground of a shot and cut them off at the waist. In stereo, that looks weird.

When you're presenting something you're always directing where someone is looking--whether its a play, movie, or stereo show. The tools are just adapted for the medium.

I do think it worked way better for movies like Avatar or How to Train Your Dragon and was less impressive for things like rom coms.

HDR in games would frequently mean clipping highlights and adding bloom. Prior the "HDR" exposure looked rather flat.

It's crazy that post is 15 years old. Like the OP and this post get at, HDR isn't really a good description of what's happening. HDR often means one or more of at least 3 different things (capture, storage, and presentation). It's just the sticker slapped on advertising.

Things like lens flares, motion blur, film grain, and shallow depth of field are mimicking cameras and not what being there is like--but from a narrative perspective we experience a lot of these things through tv and film. Its visual shorthand. Like Star Wars or Battlestar Galactica copying WWII dogfight footage even though it's less like what it would be like if you were there. High FPS television can feel cheap while 24fps can feel premium and "filmic."

Often those limitations are in place so the experience is consistent for everyone. Games will have you set brightness and contrast--I had friends that would crank everything up to avoid jump scares and to clearly see objects intended to be hidden in shadows. Another reason for consistent presentation is for unfair advantages in multiplayer.

https://iterm2.com/documentation-tmux-integration.html

Other terminal emulators offer similar features to Tmux. For example, Kitty claims to support Tmux's features outside of remote persistence.

The author talked about being very conservative on launch; skipping directories like the Photo library or others apps that actively manage data or looking across user directories. He stumbled into writing this app because he noticed the duplicated data of shared Photo libraries between different users on the same machine. That use case isn't even supported in this version. He said he plans future development to safely dedup more data--making a one time purchase less sustainable for them.

I've head some people suggest using AirPods Pro with ANC as a form of hearing protection at concerts--I think Apple might have even mentioned that in today's presentation.

The reason the parent mentioned NeXTSTEP is while MacOS between 9 and X is a ground-up rewrite if you compare those two, Mac OS X was an evolution of the NeXTSTEP codebase from 1989 (34 years ago).

> I went to the Maya developer’s conference around maybe 2002 and the devs were complaining about it being hard to maintain.

I'm not surprised. I'm a bit fuzzy on the pre-history of Maya, but I believe it incorporated software acquired from Alias, Wavefront, and TDI. However, I think part of the performance and bugginess might be from launching on expensive IRIX-based systems and transitioning to commodity hardware an Linux in the early 2000s.

I'm sure there's a lot of old niche software that feels modern and unbloated. Nuke[1] is 31 years old and Houdini[2] is 27. Maya[3] is 26 years old. I would say Maya feels bloated--but at larger places I've worked, people have avoided the newer viewports with more features because the "legacy" viewports are so fast.

It may be hard to make it feel "modern," but I love how optimized "old" code can be if they've been able to resist rewriting it.

[1] https://en.wikipedia.org/wiki/Nuke_(software)

[2] https://en.wikipedia.org/wiki/Houdini_(software)

[3] https://en.wikipedia.org/wiki/Autodesk_Maya