Jonathan Borichevskiy (via Peter Steinberger, Hacker News):
In the four months I’ve had it I’ve told at least a dozen people about it, and I’m gonna keep telling people. Being able to take my entire computing environment to places without being worried about glare has expanded the range of environments I can create in. It means I get to be in environments that are more interesting, fun, and in tune with my body.
What follows are some thoughts about how this display has fit into my day to day life in the couple of months I’ve had it.
[…]
fingerprints, splatters, and smudges are mildly annoying indoors but almost fluorescent outdoors
[…]
Closing the MacBook results in slight rubbing on the screen at the bottom of the keyboard / top of the trackpad, leaving scratches on the screen. So far this isn’t detrimental when the brightness is up; it’s only visible with the backlight off
I rarely use mine outdoors, but it even makes a big difference indoors when you don’t have control over windows and other places glare might be coming from. It’s really great on airplanes.
Previously:
Airplane Display Hardware Mac MacBook Pro
Howard Oakley:
This year marks the twentieth anniversary of Apple’s announcement of the introduction of code signing, although it wasn’t unleashed until Mac OS X 10.5 Leopard the following year (2007).
[…]
Apple had long maintained that users would remain able to run unsigned code in macOS, but that changed in November 2020 with the first Apple silicon models. Since then, all executable code run on those new Macs has to be signed. What hasn’t been mandatory is the use of a developer certificate for the signature.
[…]
Unlike some other operating systems, the only developer certificates recognised by macOS are those issued by Apple, but they’re provided free as one of the benefits of its $99 annual subscription to be a registered developer, as are unlimited notarisations.
Code signing makes a lot of sense in theory, but the developer experience still leaves a lot to be desired. It’s a constant source of annoying errors and failures, even when you aren’t changing things or doing anything non-standard. Last week, my apps stopped building because all the Developer ID certificates were expired. I have no idea why; I previously had a certificate installed that was good until June of this year.
Opening Keychain Access (which the alert at launch tries to discourage me from using) showed that that certificate was nowhere to be found. I used to keep a separate keychain file with just my developer certificates, but I’ve had to give up on that recently because Keychain Access will no longer copy items into it. It’s been unreliable at that sort of thing for years but now no longer seems to work at all.
Howard Oakley:
The general rule with security certificates is that they’re only valid until their expiry date. When the certificate for a website expires, your browser should warn you if you try to connect to that site, and it will normally refuse to make the connection as a result. Thankfully, Apple’s signing certificates generally work differently.
When Apple adopted code signing using certificates that it issues, it recognised that applying that policy would result in apps having expiry dates enforced by their certificates, so applies a different rule. When a developer signs an app using their Developer ID Application certificate, a trusted timestamp is included to verify when that signing took place. Provided the certificate was valid at that time, and hasn’t been revoked since, the certificate is deemed valid by macOS.
Apple changed that several years ago, since when installer packages have normally been given trusted timestamps, so they now work the same as Developer ID Application certificates, and can still be run successfully after their certificate has expired, provided that it was valid at the time in their trusted timestamp, and hasn’t been revoked since. However, this has only recently been reflected in Apple’s guidance to developers, and is different from the account I gave here last week.
Previously:
Anniversary Code Signing Gatekeeper History Keychain Mac Mac OS X 10.5 Leopard macOS 15 Sequoia macOS Tahoe 26 Programming
Benjamin Mayo (Hacker News):
Apple is testing a new design for App Store search ads on iPhone. Some users on iOS 26.3 are noticing that the blue background around sponsored results is no longer shown, blurring the line between what paid ad results look like and the real search results that follow.
This means the only differentiator between organic results and the promoted ad is the presence of the small ‘Ad’ banner next to the app icon.
[…]
Of course, this also has the effect of making it harder for users to quickly distinguish at a glance what is an ad and what isn’t, potentially misleading some users into not realising that the first result is a paid ad placement.
“Phenomenal customer experience.”
Previously:
Advertising App Store App Store Search Ads iOS iOS 26
