CharlesW

Nitro is wonderul. On macOS it also integrates perfectly with Photos, which I find to be an ideal "combination pro/consumer surface" for my library.

Hacker News context: Song is "co-written" using AI.

"Last month, Boy George launched a new company called Artist Included, which will use AI to allow artists to create new versions of earlier songs which resemble the originals, as a way of wresting back control of master recordings."

That sucks. I've used an LG UltraFine 5K with my Mac Studio for years and still consider it one of my favorite tech purchases ever, so I feel lucky I've never needed their support services.

The result I'm citing is very clearly presented in both a table and in supporting copy. It's even highlighted in the summary. Search for "65".

My citation was correct. To question to ask yourself: For my use case, is it okay that Pangram can't reliably tell the difference between "100% AI generated" and "AI assisted"?

Pangram's marketing always reminds me of Anchorman's Sex Panther cologne: "They've done studies, you know. Sixty percent of the time, it works every time."

Pangram's "100% AI generated" claims are right 65% of the time. https://link.springer.com/article/10.1007/s40979-026-00226-w

> A dithered image almost certainly beats a non-dithered JPEG compressed image in terms of file size, because you can JPEG compress the dithered image. Thus, if you like the look of a dithered image, you get file size reduction as a bonus.

That's backwards. Dithering (and simulated halftoning, as in this case) adds detail/noise, making images harder to compress efficiently.

> …but then it takes me 2 weekends to break up the changes into smaller commits using jj, which also gives me the chance to review and understand the code myself.

I just tell Claude Claude code, "commit all, grouping logically" after a tranche of work.

> If not, why not?

At least on Apple devices, this is not something anyone has to worry about.

For example, on my 2022 Mac Studio daily driver, on 24/7, DriveDx (https://binaryfruit.com/drivedx) reports my SSD lifetime left at 94%.

(I'm aware of the February 2021 "wear-gate" scare involving the first M1 Macs. This turned to be incorrect SSD-wear reporting.)

How was OSA/AppleScript not an OS-level malleable computing layer?

Out of curiosity, are you now or have you ever been a "Mac person"? I'm curious if you've ever gone down the rabbit hole on Apple's history of technologies for what I think you'd call "malleable computing" at the OS level, like Open Scripting Architecture/AppleScript and now App Intents?

To “yes, and” this, avoid Android Automotive. This is a different thing than Android Auto, so don't let Google's legendarily-poor product naming fool you.

Aperture (RIP) is never coming back, but many of us Aperature fans have been happily using Nitro¹, built by the guy who led Aperture and other imaging teams at Apple².

¹ https://www.gentlemencoders.com/nitro-for-macos/index.html ² https://www.gentlemencoders.com/about/

Thanks! For me, learning more about the setup for that (mostly autonomous?) build process would be more engaging than spending a minute with the result.

I know I could've done this at any time, but I cannot wait to sit my kids down in front of full-screen Oregon Trail and King's Quest experiences.

What are the broad strokes of K3's design? What did you learn?

> It would've been nice to reserve "AI" for superior human-like intelligence capable of genuine common sense and reasoning.

We've called that "AGI" since the late 90s/early 00s (depending on whether you count first use or popularization). Even if AGI does come to pass, we'll still need "AI" since not all forms of AI will be AGI.

Or if we want to be slightly more pendantic, why `libfdk_aac` (not SoundCloud per se) defaultly restricts the input's frequency range when encoding.

My guess is that this default surprised SoundCloud, and that this blog post is an attempt to (1) retroactively rationalize missing this difference with a reasonable-sounding explanation, even though it doesn't make sense at 256 kbps, and (2) create something that their support folks can point at when people complain.

Of course.

You can do `/code-review low` to more closely match Codex's default behavior.

FWIW, Via Licensing listed this patent as standards-essential to several MPEG codecs (AVC/H.264, HEVC/H.265, VVC/H.266), and it's also listed for VC-1 (a SMPTE standard).

For anyone who may not be aware it exists: https://unsloth.ai/docs/new/studio

I believe the point is that emoticons/emoji/kaomoji were never literal, and that it's surprising that anyone whose job is communications-related would say this.

Not to bikeshed, but isn't the word "mojibake" synonymous with "when character encoding breaks"?

Notably, PrismML CEO Babak Hassibi told CNBC this, so it’s either (1) bullshit, or (2) he just ended any chance of a relationship by leaking news of the talks.

> He was not annoyed about the closed garden, he was annoyed that it wasn't his.

Those are reasonable guesses, but as someone who was at Apple at the time (in developer relations, with Adobe/Macromedia among my developers), neither of those were Steve's primary annoyances with Flash. The actual annoyances were that the Flash runtime was (1) slow and (2) very crashy compared to the Windows version.

The former mattered because it created/reinforced a perception that Macs were slow. The latter mattered because it created/reinforced a perception that Macs were unstable, and it created a lot of expensive support calls. (For quite some time, the Flash runtime was the #1 cause of Mac crashes.)

There's more to this story (Adobe was threatening Apple on other fronts), but IMO Steve did the right thing by responding to a toxic partner in the way that he did.

> I don't like USB-C because they all look the same on the outside, but they're not all the same on the inside.

Many people don't realize that USB-C (USB Type-C) just refers to the physical connector. At minimum, speed and power ratings should have been required for any cable using USB-C at one or both ends. It's almost breathtaking to consider how the USB Implementers Forum has fumbled these kinds of basic issues over the years.

Close! (I had to look it up.) "The sky above the port was the color of television, tuned to a dead channel." (Neuromancer, William Gibson)

Sounds very intriguing! Please reach out (see my profile) when you're ready to share more.