Archive for April 22, 2025

Tuesday, April 22, 2025

Elegy for the Video Screenshot

Nora Deligter:

It was around this time when streaming platforms like Netflix, HBO Max, Amazon Prime, and the Criterion Channel imposed a quiet embargo on the screenshot. At first, there were workarounds: users could continue to screenshot by using the browser Brave or by downloading extensions or third-party tools like Fireshot. But gradually, the digital-rights-management tech adapted and became more sophisticated. Today, it is nearly impossible to take a screenshot from the most popular streaming services, at least not on a Macintosh computer.

The shift occurred without remark or notice to subscribers, and there’s no clear explanation as to why or what spurred the change. When asked to comment for this article, HBO claimed never to have supported the taking of screenshots and denied there had been a recent shift, while Criterion declined to comment entirely. This obfuscation raises many questions. On the one hand, if we were never entitled to screenshot, why did we have tacit permission for so long? And what do the consequences of such a policy shift look like legally, culturally, and emotionally?

[…]

The ability to reappropriate an image (and then distribute it) has long been a topic of fervent debate in the art world, surfacing again and again as a question of controversy and litigation. One such case, Andy Warhol Foundation v. Goldsmith, recently made its way to the Supreme Court. The photographer Lynn Goldsmith sued the Warhol Foundation for reappropriating an image she’d taken of the musician Prince in 1981. The Warhol Foundation argued that the resulting image was transformative rather than derivative, ill-defined terms in the fair-use doctrine that compels judges to rule subjectively on what can and should be considered art and what can’t and shouldn’t be. In the course of this case, the very definition of fair use was reconsidered. Last week, the Supreme Court concluded the case with a 7-2 decision in favor of Goldsmith, ruling that Warhol’s prints were in fact an infringement of the photographer’s copyright. Justice Elena Kagen, a member of the minority, voiced her dissent: “It will stifle creativity of every sort. It will impede new art and music and literature. It will thwart the expression of new ideas and the attainment of new knowledge. It will make our world poorer.”

But, reappropriation aside, we’ve also lost the ability to take screenshots and not distribute them. Surely that’s fair use. And, anyway, it shouldn’t be for the platform vendor to determine. This is the equivalent of preventing you from selecting potentially copyrighted text and copying it to the clipboard, which works pretty much everywhere except in the Mac App Store.

Via John Gruber (Hacker News):

I’m not entirely sure what the technical answer to this is, but on MacOS, it seemingly involves the GPU and video decoding hardware. These DRM blackouts happen at such a low level that no high-level software — any sort of utility you might install — can route around them. I think Windows still offers easy screenshotting of frames from DRM video not because the streaming services somehow don’t care about what Windows users do (which, when you think about it, would be a weird thing not to care about, given Windows’s market share), but because Windows uses a less sophisticated imaging pipeline. Or perhaps rather than less sophisticated, it’s more accurate to say less integrated. These DRM blackouts on Apple devices (you can’t capture screenshots from DRM video on iPhones or iPads either) are enabled through the deep integration between the OS and the hardware, thus enabling the blackouts to be imposed at the hardware level. And I don’t think the streaming services opt into this screenshot prohibition other than by “protecting” their video with DRM in the first place. If a video is DRM-protected, you can’t screenshot it; if it’s not, you can.

[…]

What I don’t understand is why Apple bothered supporting this in the first place for hardware-accelerated video (which is all video on iOS platforms — there is no workaround like using Chrome with hardware acceleration disabled on iPhone or iPad). No one is going to create bootleg copies of DRM-protected video one screenshotted still frame at a time — and even if they tried, they’d be capturing only the images, not the sound. And it’s not like this “feature” in MacOS and iOS has put an end to bootlegging DRM-protected video content. This “feature” accomplishes nothing of value for anyone, including the streaming services, but imposes a massive (and for most people, confusing and frustrating) hindrance on honest people[…]

DeskMat 1.0

Matthias Gansrigler:

I have a new app out that lets you sweep things under the rug – virtually: DeskMat for Mac.

With DeskMat, you cover the mess of files and folders on your Desktop with a single click – and show them again in just the same way.

It makes for clean streams, screen sharing, and distraction-free work!

Matthias Gansrigler:

By default, it shows a button on your screens’ Desktops that you can click to toggle the Desktop cover. But you can also move it to your menu bar, use a keyboard shortcut, or have it trigger automatically.

[…]

DeskMat can automatically cover your Desktops when specific apps are running, or come to the foreground.

[…]

DeskMat can automatically cover your Desktops when you activate specific Focus modes.

Matthias Gansrigler:

This is a little behind-the-scenes recap of the app’s inception.

[…]

Now, there’s this “neat” API on macOS that, on first glance, appears to be made for this: NSWorkspace.shared.desktopImageURL(for: ).

But it’s completely useless.

Maybe it actually worked for a short while after its introduction with macOS 10.6, but it’s obvious nobody at Apple ever took another glance at it again after that, ever.

Instead of returning the URL to the currently used wallpaper image file, it sometimes returns the wrong image file, or a URL to the folder containing the image file… I just couldn’t get it to work reliably – especially when a dynamic wallpaper, or a shuffling wallpaper is set, it just straight out poops its pants.

Framous 1.0 and Shareshot

Jason Snell:

Some people, whether you’re in the media or software development or technical support, take and publish a lot of device screenshots. And while an image straight from an iPhone or Apple Watch looks fine, it often looks much better to be put in context by including the device it’s running on as a frame.

I think this is way overdone, but it does make sense when mixing screenshots from different types of devices.

Apple Frames is great, but it ran into a lot of limitations simply because it was a shortcut and not a full app. Fortunately, two new standalone apps take what Apple Frames accomplished to the next level. Framous is a Mac app from the developer of Dark Noise, and ShareShot is a Mac/iPad/iPhone/visionOS app from Montana Floss Co. Both apps let you control which device (right down to the color) is used as a frame, and each have their strengths and weaknesses.

[…]

Framous is much more limited—it only outputs on a transparent background and it only runs on the Mac—but it can compose multiple screenshots into a single image. I was able to drag in screen shots from an iPhone, iPad, and Apple Watch into a single canvas, and Framous automatically detected the device and added a proper frame to each one.

John Gruber:

I love it. So many little details. You can just drop a screenshot in and copy a framed version out with zero fuss, but there are also all sorts of tweaks and adjustments you can make, right down to choosing which shade of titanium to color your specific iPhone Pro model.

Automating Screenshots for the Mac App Store

Jesse Squires:

Meeting the requirements for screenshots is a frustrating experience. On iOS, tooling like SimulatorStatusMagic, Nine41, and fastlane snapshot help make the process easier. However, on macOS there is much less support (and, sadly, demand) for automated tooling — so you are kind of on your own to figure it out. I spent some time recently solving this process for myself. I want to share how I have managed to automate perfect screenshots for the Mac App Store.

[…]

As of Xcode 9, Xcode UITest allows you to capture screenshots during tests. This is the API that fastlane uses under-the-hood for iOS. Again, because fastlane is not an option for macOS, you can implement this yourself. Xcode makes this process rather simple and easy. Here’s a helper method that saves a screenshot.

[…]

The screenshots from XCUITest have ugly artifacts in the window corners. They are not correctly cropped and clipped with a transparent background, like when you take a screenshot via the built-in functionality in macOS.

[…]

Using Retrobatch, I created a workflow to round the corners. Through trial and error, I arrived at a corner radius of 24 points.